Meaning '&' character second bottom line

Asked by Michael

I would like to know the meaning of the '&' symbol at the second bottom line (line that displays the active windows of screen).
I know the '*' refers to the active window, but there is sometimes a '&' symbol post the '*'.
Example:
0*& mutt 1- bash Menu:<F9>

Window 0 (which I have named 'mutt') has in this example the '&' character post of the '*' mark.

What means the ampersand '&' ?
I cannot find it clearly described in the screen man page or the info page of screen.

I am confused because it is not a job which has in my believe the '&' mark in bash (forgive me if i am incorrect)

Thanks in advance

Question information

Language:
English Edit question
Status:
Solved
For:
byobu Edit question
Assignee:
No assignee Edit question
Solved by:
Michael
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
Dustin Kirkland  (kirkland) said :
#1

See the screen(1) manpage, search for '&'.

 * http://manpages.ubuntu.com/manpages/jaunty/en/man1/screen.1.html

:-Dustin

Revision history for this message
Michael (m-gruys) said :
#2

Yes I did. The only thing I could find was in the beginning of of manual which state:
"windows occupied by other users are marked with ‘&’;
This is NOT true in my case. The window marked with the '&' is occupied by the same user as all the other windows (which have no & token).
Hope anyone can explain this to me.
---michael

Revision history for this message
Dustin Kirkland  (kirkland) said :
#3

Do you have multiple screen sessions open? I see the & pop up by my
window name when I open a second session and switch to that window.

:-Dustin

Revision history for this message
Michael (m-gruys) said :
#4

No Sir. Just ONE screen session with multiple windows. That's the weird thing :-). Anyway thanks for your quick light on it!
It is not THAT important, so hopefully (we) I find out someday.
Thx & regards
---michael

Revision history for this message
Michael (m-gruys) said :
#5

oeps. I see the status is solved :-(. In my opinion it is not fully clear yet.

--Michael

Revision history for this message
Michael (m-gruys) said :
#6

Problem SOLVED.
You were right sir. There was another screen session open (very old one)
Thank you

--Michael