On Tue, Jan 22, 2008 at 12:08:24AM +0100, Alex K wrote:
> Is there any way splitted windows could be preserved across sessions?
> If I split a window, then detach and reattach the session, all my
> splittings are lost.
We're working in that feature...
Cheers,
Michael.
--
Mic
e patched to use those sequences as well. That
would be in the ScrollV() function in display.c. It currently checks
if the xs/xe values cover the complete terminal width (by comparing
them to vpxmin/vpxmax), if that's not the case it refreshes the
area.
Cheers,
Michael.
--
Michael Schroeder
On Thu, Sep 13, 2007 at 11:01:04PM -0400, cga2000 wrote:
> On Wed, Sep 12, 2007 at 12:31:58PM EDT, Michael Schroeder wrote:
> > On Tue, Sep 11, 2007 at 11:22:24PM -0400, cga2000 wrote:
> > > I had a couple more questions about vertical split & caption/status
> > > li
rs:
0-7: black, red, green, yellow, blue, purple, cyan, gray.
8-f: same colors, but in "bright" mode. f is white.
So "70" means black on gray, "71" would be red on gray.
>Is there any reason I would want to do so? Would they provide
>additional functionality?
Nope, same functionality.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
indow" and the right-most part of it is truncated.
The hardstatus always covers the complete width of the terminal,
are you mixing it up with the window caption?
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())put
en if that's
> so, some of the fault probably lies with screen, in mishandling the
> situation and sending NULs that it clearly is not receiving, and that
> have nothing to do with terminfo values.
Maybe 'kb' is bound to something. Try '^A:bindkey' and '^A
window. If I go
> to next window, I would see a 2x1 layout. ^a next
> would show me a 4x4 layout. ^a next would bring me
> back to the single window layout.
Sounds to me like it is exactly what the layout code does.
You just have to bind ^A to "layout next" and create
three l
put the windows from your groups on them.
Or do you need something different?
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-u
ry somehow, what is the
output of 'infocmp' before you start screen and in screen?
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing
the upper bits.
To fix this bug we'd have to change the way the string gets stored.
Note that we can't just simply transcode to the display's encoding,
as the window may be displayed on multiple displays with different
encodings...
Cheers,
Michael.
--
Michael Schroeder
gurable, so you
can then put any color codes in it that you like.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
creen is
> involved.
Yes, currently a vertical split is expensive. As screen doesn't use
any special "region-scrolling" functions of the terminals it has
to do lots of refreshes. I hope to fix that soon (at least for
xterm).
Cheers,
Michael.
--
Mic
ession.
This is because screen doesn't know which window to use for the
'exec' command. Add '-p 0' and it should work.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
_
her than a target.)
I'll try to find it.
Thanks,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
On Fri, Feb 09, 2007 at 02:07:14PM -0500, Aaron Davies wrote:
> On 2/9/07, Michael Schroeder
> <[EMAIL PROTECTED]> wrote:
> >On Thu, Feb 08, 2007 at 07:40:50PM -0500, Phil!Gregory wrote:
> >> > - vertical split, complete with resizing
> >>
> >> I&#
hen get an a-umlaut by pressing ^A:a, an o-umlaut by pressing
^A:o and so on (so you have created an "umlaut" command). That's
also why the old table has:
s " -> LATIN SMALL LETTER SHARP S (German)
So it probably
;s just a matter of setting up the
"viewports" in the "canvas". Compile screen with -DHOLE to get
another example of a non-standard layout.
How about the other screen users? Do you think it's worth to
implement something like this?
Cheers,
Michael.
--
Michael Schroed
e)
- some code using sockets (complicated)
- using /proc// to access the file descriptors of your
process. But that's not very portable. Something like:
open my $SCREEN, qq{screen -t 'Child $$' sh -c "tty >/proc/\$\$/fd/1 ;
sleep 100" ; sleep 10 |}
so on.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
our ~/.screenrc. If you
need a new Desktop, do "^A:layout new Desktop2". You can then
use "layout next" to switch between both layouts.
So, feedback welcome. You probably have a lot of suggestions and
enhancement requests. Sorry that development is a bit slow at
the mome
screen session. Any
> daemons running are started at bootup, and don't have anything to do with
> login users.
Could be a bug in screen's utmp handling. What OS are you running?
Thanks,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(
;sz " on the host.
Screen will intercept the zmodem sequences and prompt you
with a "rz" prompt. You just confirm this by pressing return and
the file will get transfered.
Cheers,
Michael.
--
Michael Schroeder [E
get recoded?
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
sh?
It should work if you compile bash with NON_INTERACTIVE_LOGIN_SHELLS
defined. I don't think this has changed between bash-3.0 and
bash-3.1, though.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
__
tring
to a window.
The fixed version is (as usual) available via:
ftp://ftp.uni-erlangen.de/pub/utilities/screen/screen-4.0.3.tar.gz
Credits go to cstone & Rich Felker for finding the bugs.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())put
on such a "tab bar"?
Do not use screen 0, start with screen 1 instead. Make ^A0 switch to
window 10 instead of 0.
(e.g. put
bind c screen 1
bind 0 select 10
screen 1
at the end of your ~/.screenrc file)
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(
On Mon, Oct 09, 2006 at 04:45:48PM +0200, Michael Schroeder wrote:
> FYI: I'm just adding vertical split support to screen. Seems to
> work fine, what's currently broken is the "resize" command.
And yes, this means that we'll release screen-4.01 this year...
s you to treat multiple local and remote
> Screen sessions as a single seamlessly integrated session.
>
> Anyway, check it out if you're interested at:
>
>http://sourceforge.net/projects/screenwm
Sounds nice, I'll have a look at it.
Cheers,
Michael.
--
Michael Schroede
live
> connection so when another driver jumps on the original forklift the two
> drivers will be fighting for control of the one session. How can I tell
> if an "Attached" session is the result of a dropped radio link or if it
> is live?
If "screen -ls" prints &quo
OS 4.1.3 a long time ago). Those settings have erase=\177 and
kill=\b, they are hardcoded in tty.sh. Maybe Debian changed them in
the update.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
__
is if it would make sense to extend
the bell/activity/silence message handling by allowing any screen
command, instead of just showing a message.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
f exit
'
If you want to kill the window, use:
screen -S kamal -X kill
If you want to kill screen, use:
screen -S kamal -X quit
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
t in window "data".
> But I want to use the same keystrokes even if I am in the data
> window. But then I get the error message "This IS window ..."
> and an irritating 1 sec pause.
If you don't mind the extra refresh you can use:
bind r eval 'select -&
y emulation.
Screen has to fiddle with the emulation because it supports reattach
from different terminal types.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
s
ht, that one liner patch is not enough. Sorry, I confused it
with a similar bugfix.
But try
screen -S test -p one -X stuff "ls `echo -ne '\015'`"
instead, there's no need to use the 'at' command.
Cheers,
Michael.
--
Michael Schroeder
;s even a bit worse,
only root can do TIOCCONS on linux:
static int tioccons(struct file *file)
{
if (!capable(CAP_SYS_ADMIN))
return -EPERM;
The way it is done in other UNIXes makes much more sense, see e.g.
the SRIOCSREDIR ioctl in solaris.
Cheers,
Mi
minal /dev/tty12
> >> (or similar) in a window in screen?
>
> >Not entirely sure but I don't think that is possible.
>
> Probably not, no, but as I don't know I asked.
If it's just console output you're looking for you can try
'console on&#x
On Tue, Jun 20, 2006 at 10:42:32AM -0300, Germn Gutirrez wrote:
> Thanks for the info, is that a known bug or does it have to be reported?
It's obviously known ;-)
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*
>
> Msg('-X: at: display required') (0);
>
> So, the display is required in the code. May be this can be set in the
> screenrc file, any clues?
No, it's a bug in screen. Delete the NEED_DISPLAY in line 56 of
comm.c (the line for the "at" command).
Chee
#x27;d really like to avoid
> having lots of old screenrc temp files lying around.
>
> Does anyone have any suggestions on how to solve this problem?
You can also write a tmp file and then use
screen -S screen_cons -X source
to source it. You won't have the reattach problem this way.
Chee
rything fails, add "defflow off" to your ~/.screenrc file.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gn
can be implemented.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
n would
have to send the file discriptors of the windows from the old session
to the new one. Unix domain sockets may provide this functionaltity.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|
ranslated. Not portably usable by apps. But [backspace]?
Actually this is a missing feature: screen should translate all of
the stty settings. Not implemented yet, though. We currently hope
that the stty setting used when screen was started is the same
when the user reattaches.
Cheers,
Michael.
--
M
ation.
Actually I don't know a single application that looks at kbs. The
right way is to check the ERASE stty setting.
You should check for some bogus 'bindkey -k kb ...' line in the
system screenrc file and the .screenrc in your home directory.
Cheers,
Michael.
--
Michael Schroe
to screen, the \007 ends
the sequence for the xterm.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
ODO list for
a long time, but it's still not implemented.
Sorry,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
dd
termcapinfo putty* XT
to your ~/.screenrc.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.o
tially break something?
No, it can't break things, but it needs a little bit more memory.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing
hat do you folks think, shall we release an "interim" version
where some of the things we wanted in the next release are still
missing?
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar
x27;t want to detach from screen because I want to see what the
> program's doing (when I'm not lagged out).
Maybe the 'nonblock' and 'defnonblock' commands help here.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
ma
On Thu, Feb 02, 2006 at 09:58:15AM -0600, Aaron Griffin wrote:
> On 2/1/06, Michael Schroeder
> <[EMAIL PROTECTED]> wrote:
> > A screen-256color terminfo entry is probably the way to go...
>
> And possibly a screen-88color terminfo entry too... urxvt and a
> handful
rm understands more colors.
The other part is to tell the applications that screen knows them.
A screen-256color terminfo entry is probably the way to go...
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
__
ces. Vim currently checks if $TERM
eq 'xterm' and does a version query to check if the xterm version
if new enough. vim should be patched to be able to deal with
screen.
Hmm, maybe screen should also be patched to try a xterm query.
But AFAIR default xterm doesn't support it.
Che
windowlist commands are ignored because windowlist is marked
as "NEED_DISPLAY" in comm.c by mistake. "source foo" should work.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
think any of the commands actually output to
> stdout when run from the command line. Might be a nice thing to hack
> in though.
You can use 'screen -X writebuf ' to dump the copy
buffer into a file. If you need stdout dump the content into a
tempfile and write the tempfile to st
o, currently you can only "reset" screen's internal window state.
> I had to quit screen completely to recover.
Detaching and reattaching should also help.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())put
f I should wait for a complete implementation
or not. What are your feelings about this?
> The more I get into this code, the more I like it. It's a very nice
> design.
Thanks!
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
Btw, here's the current status:
On Sun, Dec 18, 2005 at 04:38:36PM +0100, Michael Schroeder wrote:
> Planned features for the next release:
>
> - sending the tty file descriptor from the frontend to the
> backend over the unix domain socket, so you won't get error
>
n screen reight away. You have to add resizing, stacking and the
like. Just habe a look at vim.
(And please don't use EXIT_FAILURE/EXIT_SUCCESS, we're all using
unix here. I much prefer 0/-1)
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main
y in "HEAD".
Micha.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
On Mon, Dec 19, 2005 at 12:42:10AM +0900, pclouds wrote:
> On 12/19/05, Michael Schroeder
> <[EMAIL PROTECTED]> wrote:
> > On Sat, Dec 17, 2005 at 08:30:09PM +0900, pclouds wrote:
> > > I'v read somewhere that screen has stopped development, only
> > >
On Sat, Dec 17, 2005 at 08:30:09PM +0900, pclouds wrote:
> I'v read somewhere that screen has stopped development, only
> maintainance. Is it true?
No! Who says such things?
Micha.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/
x domain socket, so you won't get error
messages after an 'su' to a different user.
- creating a little suid-root multiuser helper, so that multiuser
mode doesn't need the big screen binary to be suid-root.
- a couple of minor improvements
uded?
Depends on the patch. If it is not too ugly, then yes.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://
iletime that you want
> either at the top or the
> bottom but both I couldn't find..
There's TOPSTAT in config.h, which moves the status line to the top.
But you can't have a status line both on top and the bottom of the
screen with the current code.
Cheers,
Michael.
--
Michael
"screen.linux"
Uh huh. The Fedora guys are strange. Try:
mkdir /usr/share/terminfo/s/screen-backup
mv /usr/share/terminfo/s/screen.* /usr/share/terminfo/s/screen-backup
I don't see why you would need those extra terminfo entries.
Cheers,
Michael.
--
Michael Schroede
#x27; aka termcap 'is' string.
You can use screen's termcapinfo command to set it to a string without
the resize part.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
to_get something (e.g. fetchmail -c)
> echo something
> sleep some time
> done
It should work if you use just echo, as this is a shell builtin.
If that 'echo something' is an external command or a pipe you have
to use 'echo something || exit 1'.
How exactly does the
ager.
Du you check the exit status of your commands?
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
a functionality and screen won't complile with some older
compilers anymore. It's the same thing as throwing out support for
old OSes, it's just a bunch of ifdefs that doesn't hurt much.
Cheers,
Michael.
--
Michael Schroeder [EMAIL
On Mon, Sep 19, 2005 at 09:56:02AM -0500, Aaron Griffin wrote:
> On 9/19/05, Xavier Nicollet <[EMAIL PROTECTED]> wrote:
> > Le 15 septembre 2005 ? 19:26, Michael Schroeder a ?crit:
> > > Now that's a good question. I'd love to spend much time for screen,
> >
On Thu, Sep 15, 2005 at 12:51:38PM -0500, Aaron Griffin wrote:
> On 9/15/05, Michael Schroeder
> <[EMAIL PROTECTED]> wrote:
> > Planned features for the next release:
> > - maybe vertical split, if I still have some time left.
>
> Hooray! Out of morbid curiosity,
fter an 'su' to a different user.
- creating a little suid-root multiuser helper, so that multiuser
mode doesn't need the big screen binary to be suid-root.
- a couple of minor improvements, like the input buffer problem.
- maybe vertical split, if I still have some time left.
Cheers,
M
to another host and try to
> paste text into vi, there's a lot of text loss. It happens with rlogin as
> well.
This happens when screen's input buffer is full. Known problem. I'll
try to fix it in the next version of screen.
Cheers,
Michael.
--
Michael Schroeder
Let's ask screen-users@gnu.org if somebody with HPUX experience
knows what's going on here.
Cheers,
Michael.
- Forwarded message from Carlos Vanegas <[EMAIL PROTECTED]> -
> I installed screen-4.0.2 in HP-UX 11.11 (in format depot) and I ran
> screen very good the last Thursday , I m
to close and
reopen the pipe to clear the EOF status. If the second 'screen -X'
is fast enough it will write to the old pipe and thus get lost.
You can either
1) recompile screen to use unix domain sockets, or
2) recompile screen with BROKEN_PIPE defined in config.h, or
3) use the 'e
On Fri, Aug 12, 2005 at 10:26:08AM -0700, Trebor Sreyb wrote:
> --- Michael Schroeder
> <[EMAIL PROTECTED]> wrote:
>
> > Okay, start screen and press ^V F10 (^V is Control
> > V). Then do 'infocmp screen' and check if the kf10
> > entry matches this s
, start screen and press ^V F10 (^V is Control V). Then
do 'infocmp screen' and check if the kf10 entry matches this
string (\E is ^[). (The string should be "^[[21~", btw.)
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=
try is wrong, it should probably read
WS=\E[8;%p1%d;%p2%dt'. If the codes are always the same we wouldn't
need two different commands...)
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
%-F or %!F to expand to true when a window does *not* have
> focus. This would allow the following types of sequences:
> "%?%F%:non-focused window string escapes%?"
> "%?%-F%:focused window string escapes%?"
This is acually already
On Mon, Jul 18, 2005 at 07:37:58AM -0400, Thomas Dickey wrote:
> On Mon, 18 Jul 2005, Michael Schroeder wrote:
>
> >On Mon, Jul 18, 2005 at 06:25:24AM -0400, Thomas Dickey wrote:
> >>The code's doing what it is intended: when screen is running in UTF-8
> >>mode,
ce was a version of screen that
ignored termcap information, but this got changed a long time ago...
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users
e screen. Is there actually a valid reason for ncurses to do this
> test?
Don't ask me, I'm not aware of any problems screen has with UTF-8.
Maybe Thomas Dickey, the ncurses author, can shed some light on
this.
(CC to [EMAIL PROTECTED])
Cheers,
Michael.
--
Michael Schroeder
$SYSSCREENRC, I would expect the
> effect from both within and without screen to be the same.
Setting the escape character does an implicit bind for the "other" and
"meta" command. It's just a problem of the order: if you do it in
screen, the screenrc file is already pro
uld change the code so that the password query is done by
the backend, but what happens if the backend dies (e.g. because you
attached from somewhere else and killed the session)? In that case
the frontend must not fall back into a shell.
With other words, it is doable, but it's not a sim
as to quit screen and so many users complained about killing
their precious session by mistake.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users ma
On Sun, Jun 19, 2005 at 07:39:09PM +0200, Michael Schroeder wrote:
> 2) font
>
> the font information is basically just the ISO-2022 character
> set numbers plus some extensions. 0x00 is always the "default"
> font.
>
> size 94:
> 0x30 (0) Alte
lace to store the most significant byte. I.e.:
utf8char = image | (font << 8)
Combining characters are recoded to the range 0xd800-0xdfff.
The real string is stored in the "combchars" array.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getcha
oesn't
dump colors/fonts/atrributes.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailm
|xterm-xmc|xterm alias:sg#1:tc=xterm:
In other words, they don't support the color codes. But maybe your
termcap contains different entries.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
__
On Mon, Apr 25, 2005 at 09:08:42AM -0400, Andy Goth wrote:
> On Mon, Apr 25, 2005 at 12:23:12PM +0200, Michael Schroeder wrote:
> > Pressing ^S ^A ESC will hang screen (on linux).
>
> Yes, that works. Hehehe, what a funny definition of work.
>
> Now I know what to avo
ut reconnecting doesn't cause failure to reattach. But I have seen
> hang on reattach before, so I must have the problem in some form.
Pressing ^S ^A ESC will hang screen (on linux).
Cheers.
Micha.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_
, only a workaround. The real fix is to change
the Msg() implementation so that it doesn't need the Flush().
Actually, all calls to Flush should be removed...
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~
screen doesn't
> change that. Would be very nice to have this under screen since my vim
> colorscheme needs 256 colors.
You have to define COLORS256 in config.h...
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar
se=xterm2' should do the trick.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
completely different. xterm & vim do it right, vim
uses an escape sequence to ask xterm about its capabilities. In other
words, the terminfo entry should be stored inside of the terminal.
(A first step would be if tools like ssh would "forward" the terminfo
entry if one logs into
apple."
The normal select command (aka ^a') already works with prefixes,
i.e. ^A'ap will switch to window "apple". You're suggesting
a search funktion for window lists. Yes, would be nice, and it
was requested by some uther users as well...
Cheers,
M
een? Mine is
> > "xterm" and I am using the UTF-8 character set (this is in PuTTY).
>
> After starting screen, here's the terminal information:
>
> TERM=screen
> TERMCAP=SC|screen|VT 100/ANSI X3.64 virtual terminal:\
>
> Is that useful?
Hmm,
t; selected in the bottom.
Good idea, I'll implement this. (Or does somebody else object to this
proposal?)
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
sc
1 - 100 of 102 matches
Mail list logo
