Fwd: Why does "\024" mean `C-t'? (in bindkey example in man page)

Resending; meant to send this to the list, not privately. On Sun, Aug 14, 2016 at 7:11 AM, Aleksey Tsalolikhin wrote: > > Lovely, thank you very much Axel and Pieter! > > Why does pressing ctrl-1 make 1, and pressing ctrl-3 make ^[ ? Pressing > ctrl-8 makes nothing,

Today's XKCD

Features screen. :D http://xkcd.com/686/ -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. Maintainer of GNU Wget and GNU Teseq http://micah.cowan.name/ ___ screen-users mailing list screen-users@gnu.org

Re: modifying terminfo via termcapinfo

Joahnn Gile wrote: So what's wrong here, is termcapinfo not modifying the terminfo entry? You seem to be misunderstanding the purpose of termcapinfo. Its purpose is not to modify actual termcap or terminfo entries, in particular the ones that other applications might see and modify behavior

Re: Function keys in htop?

SMaddox wrote: I apologise if this is a stupid question, but I have been searching for the past hour and am going crazy because I can't find the answer. How do you pass function keys (F1,F2,etc) on to htop through screen? Neither 'F3' nor 'C-a F3' brings up search in htop as it should. On

Re: Missing GNU Screen maintainer

Micah Cowan wrote: Our beloved maintainer Sadrul Chowdhury has apparently been missing since mid-July. And has since returned. Looks like he's well, and back, sorry for the alarm. :) -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. Maintainer of GNU Wget and GNU Teseq

Re: Scrolling performance in vertical split-screen mode - screen vs. tmux

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Jones wrote: I was evaluating tmux over the weekend and though I'm not prepared to switch any time soon, I couldn't help but notice that tmux's scrolling in vertical split screen mode is both very fast and devoid of the annoying artifacts

Re: who am i on screen

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tales Macedo wrote: Good Afternoon Friends, Why the command who am i don't work on screen ? That's very unlikely. Why don't you tell us exactly what you're trying, what you're seeing, and what you expected it to do that differs from the actual

Re: who am i on screen

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Please keep it on the list) Tales Macedo wrote: Thanks for answer me Initially excuse my english. When I try to run the command $ who am i on screen session, it does not show anything. Type: $ screen (on screen session I

Screen documentation tasks identified

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, as the documentation seems to be one of the biggest remaining obstacles to a 4.1.0 release of GNU Screen, and as it's been this way a very long time, I've taken one step towards trying to ease the prospect of getting this work done. I've gone

Re: How Can I Disabled Ctrl + A..B...C

I'm afraid I really don't know what you're asking for. Details? Tales Macedo wrote: Good Evening, How Can I Disable Ctrl + a,b,c,d key functions on Screen ? ___ screen-users mailing list screen-users@gnu.org

Re: multi-user screen: switching windows isn't reflected in screen instances

David Chanters wrote: Hi all, I like the feature of multi-user screen. I often do this via: screen -x -S somesessionname And it works great -- until, that is, I change windows in screen (via ^a a, or ^a 1 -- where 1 could be any number depending on the number of windows in screen). As soon

Re: how to use process?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 clemens fischer wrote: clemens fischer wrote: is there a way to evaluate this register as screen commands? Thank you very much, Gerald Young and Micah Cowan! Looking at my older, unanswered article I think I had a bad, unclear example

Re: how to use process?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 clemens fischer wrote: On Thu-2009/04/30-16:47 clemens fischer wrote: Recently I needed a screen command sequence more complex than the usual key bind or stuff. I turned to process [key], as the man page said: command can be used to bind

screenenv: make screen use the right display and ssh agent

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://log.or.cz/?p=39 I would have opted for proxying instead of library call hijacking, but anything's better than nothing. Worth looking at. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. Maintainer of GNU Wget and GNU

FYI: was out of contact 4/15 - early June

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, the email address with under I was subscribed to the screen lists expired without my noticing. It was an email address I'd received for being a member of a group, and that membership had expired. I had not realized that this would mean I would no

Re: security issues with screen setuid root

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Nitsche wrote: Hello list! I'm new to this list and here's my first question. I'd like to know which security issues are important when I'm setting screen setuid root. I tried that on one maschine to use the multiuser feature of

Re: Vertical Split

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Terry wrote: I'm confused. I read online that vertically splitting a window was available as of 4.00.03, which is what my screen version claims to be, yet when I type ctrl-a | (which means hold down ctrl and a, then release and press shift

Re: backtick with colors

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 JuanPablo wrote: hi, I try make a backtick with automatic change of colors example #!/bin/bash #file name sbacktick cadena=Bright red on white echo -e \033[47m\033[1;31m $cadena \033[0m in screenrc backtick 1 60 60 $HOME/bin/sbacktick

Re: when running vim under Solaris, terminal doesn't refresh properly

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Langella Raphael wrote: Hi, I'm running GNU Screen 4.00.02 under Linux RHEL 4u5. vim works fine under Linux, but if I ssh to a Solaris machine from within screen, then I've got some problem with vim. When I edit a file, I've got some garbage after

Re: screen questions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 lehe wrote: Hi, Two questions about screen: 1. I was trying to switch from scroll back mode to command line mode by C-a :. However instead a : is at prompt and seems ready to recieve what I'll type. So which mode did I enter actually and how to

Re: misc.c:619: error: too few arguments to function `setenv'

iEYEARECAAYFAknOogYACgkQ7M8hyUobTrGhQgCcCJMmBCivjAwZVsO3uFu9Cu2q 0O0AoIedicwNOFwLLxEQc8WYTgO6fmsd =99jc -END PGP SIGNATURE- commit 2cc00bf4d858ce36ff80b51560a795fb48303228 Author: Micah Cowan mi...@cowan.name Date: Thu Aug 7 22:10:08 2008 -0700 Proper 2-arg/3-arg setenv checks (#15921). diff --git a/src/acconfig.h b/src

Re: problems with mutt and xterm-title (new user)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ssiza...@gmail.com wrote: I've been playing around with screen for the last two days and like it so far. But there is one thing that bothers me: When I start mutt from my shell (bash, with gnome-terminal), the terminal title changes to mutt: =

Re: screen, PuTTY, and kernel config

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Lieb wrote: Florian Bender wrote: Chris Lieb wrote: I have run into two issues getting screen to work with the Linux kernel configuration utility (make config). First, in PuTTY, the display is garbled when the config utility is running.

Re: screen, PuTTY, and kernel config

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Lieb wrote: Micah Iowan wrote: GNU ncurses has a specific entry for putty, so you might want to tic the latest terminfo definitions from ncurses (it's in a file named misc/terminfo.src, IIRC). And then, of course, have PuTTY set TERM to

Re: changing location of uscreens/ ?

I don't know what you mean by is working perfectly, but just because you place your screen sockets directory in a persistent location doesn't mean that your screen sessions will persist across a reboot: they simply cannot. -mjc Pau wrote: no, actually the --with-socket-dir option is

Re: Using the numpad in nested screens

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Lieb wrote: I am a new screen user and have run into a problem. When I ssh into a server, screen automatically starts, just as I want. The number pad works without issue. I then ssh into another server, where screen also automatically

Re: changing location of uscreens/ ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pau wrote: Hello, I was wondering whether it is possible to change the location of uscreens from /tmp to some other place, because it gets deleted everytime the computer boots, which it does, because it is a laptop. It would be very useful to

Re: bind pgup key to scrollback

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Asif Iqbal wrote: Hi from my screen window I tried to bind the pgup key to scrollback like this :bindkey -k kP copy After that I hit `pgup' button and I get a `~' instead of expected scollback behavior. Most likely the terminfo/termcap

Re: bind pgup key to scrollback

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Asif Iqbal wrote: On Wed, Mar 4, 2009 at 3:39 AM, Micah Cowan mi...@cowan.name wrote: - What is the output of the infocmp command # Reconstructed via infocmp from file: /usr/share/lib/terminfo/x/xterm xterm|vs100|xterm terminal emulator

Re: Using the numpad in nested screens

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Lieb wrote: Micah Cowan wrote: Chris Lieb wrote: I am a new screen user and have run into a problem. When I ssh into a server, screen automatically starts, just as I want. The number pad works without issue. I then ssh into another server

Re: Using the numpad in nested screens

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Lieb wrote: Micah Cowan wrote: Try adding the line: terminfocap screen* ks@:ke@ to your final destination host's ~/.screenrc or /etc/screenrc, and see if that makes a difference in (freshly started) screen sessions. I added

Re: Using the numpad in nested screens

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Lieb wrote: Micah Cowan wrote: The \E[?1 sets cursor key mode, and the \E= sets application mode. You may possibly want to keep \E= if it doesn't screw things up, so now try changing the line to: termcapinfo screen* ks=\E=:ke=\E

Re: Using the numpad in nested screens

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Lieb wrote: Micah Cowan wrote: Try adding the line: terminfocap screen* ks@:ke@ to your final destination host's ~/.screenrc or /etc/screenrc, and see if that makes a difference in (freshly started) screen sessions. I added

Re: changing the socket name?

Aaron Davies wrote: is it possible to change the socket name of an existing screen? C-a : sessionname newname RET -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. GNU Maintainer: wget, screen, teseq http://micah.cowan.name/

Re: changing the socket name?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aaron Davies wrote: btw, the note in the manual _Caution_: The `$STY' environment variable still reflects the old name. This may result in confusion. The default is constructed from the tty and host names. could be a little

Re: Screen manual online

Micah Cowan wrote: I find the index of commands from the texinfo-based docs to be _particularly_ handy. You might want to bookmark that page: http://www.gnu.org/software/screen/manual/html_node/Command-Summary.html Hm, guess I actually meant this one: http://www.gnu.org/software/screen/manual

Laptop kaput

Well, my primary system is toast now, so my activity level may drop dramatically (which is perhaps saying something :) ) for the next couple of weeks. Sorry! -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. GNU Maintainer: wget, screen, teseq http://micah.cowan.name/

Re: using screen logs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jae Norment wrote: I use screen to log sessions where I patch Debian servers. Screen captures ANSI control codes (like positioning and color changes), which is probably appropriate, however, I want a version of the logs without those codes so

Re: capturing the bell

JuanPablo wrote: Micah, many thanks for you reply. is posible capture of similarly the alerm messages of screen ? Unfortunately, I don't know of a practical way to do this. Perhaps someone more clever than I will think of something. -- Micah J. Cowan Programmer, musician, typesetting

Re: time formatting?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 William Pursell wrote: William Pursell wrote: Aaron Davies wrote: ok, here's a patch (i can't get github to work so this is against the tarball http://www.wpursell.net/screen-4.1.0w.110-349d.tar.gz) the github address I gave is wrong. Micah

Re: capturing the bell

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 JuanPablo wrote: hi, is posible capture the bell of screen in other program? example: if screen launch a bell, the dialog program is called dialog --msgbox hello world 6 25 thanks JuanPablos Try C-a : exec :.. /path/to/filter.pl RET

Re: EOL switch?

Leslie P. Polzer wrote: I could only observe this problem with screen and long-running (or often typed-into) sessions of SBCL. But I hardly run any other program in Screen... Didn't you say you could reproduce it in other apps as well, thus ruling out the app? -- Micah J. Cowan Programmer,

Re: updating the build

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've slightly rearranged the order of your text somewhat, for my own convenience in responding. I apologize for taking so long to respond to your steady sets of patches and notices on this. And particularly, for promising to set up a hosted

Re: GNU Screen split vertically

Grigorios Bouzakis wrote: On Sun, Jan 11, 2009 at 12:55:19AM -0800, moueza wrote: Ctl-A AltGr-| makes nothing GNU screen cant split vertically by default. Theres a patch for it though: http://fungi.yuggoth.org/vsp4s/ The current git sources at Savannah can. And it's a different

Re: control

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 broz wrote: On Thu, 04 Dec 2008 10:02:31 -0800 Micah Cowan mi...@cowan.name wrote: broz wrote: Hi, i have a question about gnuscreen which I think is great btw. I may have a hard time conveying what I want to know, but here goes: I

Re: Cursor shape with ncurses programs gets reset

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Wood wrote: I have a flashing block cursor set up because I find it very hard to see the normal _ underline cursor - expecially when searching through man pages etc. The problem comes when I run ncurses programs in screen. The cursor gets

Re: ;screen printed in top left corner

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Wood wrote: On (16:32 19/12/08), Dave Wood d...@unrealize.co.uk put forth the proposition: On (18:54 18/12/08), Dave Wood d...@unrealize.co.uk put forth the proposition: I find after switching screens a few times that I get either ';screen'

Re: Is there any way I can split long lines in .screenrc?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Jones wrote: Couldn't find anything in the usual repositories. Here's my current hardstatus line (length=190): hardstatus alwayslastline %{+r wk}%H %{+b yk}%0` %{+b wk} %1` | %2` %3` |%4` %{+b wk}| %{+b wk}%l%{+b wk} |%{+b gk} %n %t

Re: screen -X

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Mahoney, System Admin wrote: Which reminds me -- in looking for docu on this subject and others, I found the gnu.org screen page, and the only thing there is links to the mailing list. Are there no official web-docs? FAQs? Or are they all

Re: help to use screen command

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Trent W. Buck wrote: Micah Cowan [EMAIL PROTECTED] writes: screen sh -c vim `find . -name '*.c' -o -name '*.cpp'` title vim FWIW, sh -c 'vim find . -name \*.c -o -name \*.cpp -exec vim {} +' would be better, if your system supports POSIX 2003

Re: screen -X

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Mahoney, System Admin wrote: On Sat, 6 Dec 2008, Micah Cowan wrote: As to FAQs, there's one on the wiki page that someone set up for the IRC channel (apparently?). I should put a link to that on the gnu site as well: http://aperiodic.net

Re: screen -X

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Lloyd wrote: The -X option seems like it's intended for this purpose, but it seems to be a no-op. The man page says Note that this command doesn't work if the session is password protected. To my knowledge the session is not password

Re: control

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (sorry, accidentally hit Reply instead of Reply All) Micah Cowan wrote: broz wrote: Hi, i have a question about gnuscreen which I think is great btw. I may have a hard time conveying what I want to know, but here goes: I currently use

Re: help to use screen command

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zaphod wrote: Hi 1st of all, i am using screen for number of years now and like it very much. lately decided to upgrade my environment. So my question is. Using .screenrc file where wants to open window with vim. The vim should also open

Re: Raggle

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Mahoney, System Admin wrote: Is it possible to define viewer commands in Alpine that would do either of the following: 1) Launch in a separate window and/or 2) set the title correctly? Right now, my shell seems to step in and want to set

Re: Problem running screen in chroot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 head0r wrote: Hi, i tried putting screen in a chrooted environment. I copied the /etc/passwd and the libs listed by ldd /usr/bin/screen. But when i try starting the screen in the chroot, i get the following error message: getpwuid() can't

Re: Screen output get cut!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sheepa.org wrote: * Since the playlist never gets cut when im writing in manually I'm thinking this is some kind of screen -X stuff problem? * * * It's unlikely to be related to the actual screen -X stuff command. It's possible that there's a bug

Re: Is it something I said? re:locking

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Mahoney, System Admin wrote: All, I apologize if I've argued a bit fervently in the past for what I felt was a simple feature (i.e. support for screen to also use the attach password as a lock password on systems that do not support either

Re: Bigger annoyance with locking.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Mahoney, System Admin wrote: On Thu, 13 Nov 2008, Trent W. Buck wrote: Micah Cowan [EMAIL PROTECTED] writes: Dan Mahoney, System Admin wrote: According to the manpage, screen calls /bin/lock or whatnot -- there's no way through .screenrc

Re: backspace and tab broken?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pia Mikeal wrote: Greetings, I am not sure if this is a bug in screen or something else, but screen seems to be a package I can take out of the equation and the problem goes away. Here is my issue, at the commandline, my virtual terminal

Re: Binding a multi-key sequence to a multi-command

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gorsuch, Ryan wrote: The manual indicates that I can bind several commands to a key using the process command but no examples or syntax are given. What I'd like to do is bind the sequence: C-a s 1 to the commands: split, focus, select 1 using

Re: Silly question about lock

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Mahoney, System Admin wrote: hey, is there a way to customize the message displayed on the lock, for example: Whether it was locked by time, or idle? What time it was locked? What HOST it's running on? These could all be managed now,

Re: Bigger annoyance with locking.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Mahoney, System Admin wrote: According to the manpage, screen calls /bin/lock or whatnot -- there's no way through .screenrc to change this (why?)...and yet the output of a locked screen looks significantly different from when I use lock alone.

Re: problem with screen.rxvt TERM and less

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henry S. Thompson wrote: Micah Cowan writes: Oh, is that the problem? Screen has its own built-in alternate screen buffers; just add the altscreen command to your ~/.screenrc. D'oh! That fixed it. Thank you for your patience

Re: sending CRLF via screen -X stuff

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Elliot wrote: Hello, I am trying to send a remote command to an existing screen session: while true; do screen -S 19268 -X stuff signon; sleep 1m; done However, I need to send a new line (CRLF) after the command signon. Chances are

Re: problem with screen.rxvt TERM and less

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henry S. Thompson wrote: Micah Cowan writes: I'm not entirely sure I understand what the symptom is that you're describing for running less under the screen-managed window, but it sounds like it might be similar to this one, which is fixed

Re: problem with screen.rxvt TERM and less

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henry S. Thompson wrote: I built screen 4.0.3 from source, with cygwin patches, on cygwin, with ncurses 5.7, and rxvt for my terminal emulator. The 'less' program has an irritating fault in this configuration which I can't figure out how to work

Re: Setting window title in ssh'ed host

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robin Lee Powell wrote: On Wed, Nov 05, 2008 at 02:39:13PM -0800, Micah Cowan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gokdeniz Karadag wrote: Hi, This is more like a story, I am trying to automatically set GNU screen window

Re: screen with irssi, sux.theme, urxvt

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Herz wrote: Hi, i have a confusing problem. I have a debian testing system. I use urxvt on my desktop, then ssh to the server with irssi running in screen. I also use the sux.theme from the irssi.org page. Now i found out, that in the

Re: Screen Issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robin Lee Powell wrote: On Wed, Oct 29, 2008 at 10:56:52PM -0500, Clint Priest wrote: 1) Is there any way to get 'quit' to work from the bash command line? Have it kill the parent process, which should be the screen session. 'screen -X quit'

Re: config to get screen to never touch the hardware status line in xterm

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Tang wrote: Hi folks. I've been reading on google and in the archives about how folks do cool things with the hardstatus and hardware status line in xterms. I'm trying to do exactly the opposite...I want screen (when used in a terminal

Re: Promote Screen? Include .screenrc!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Marsh wrote: A simple .screenrc file that opened two windows with shell in each, plus a nice simple hardstatus line might have help me to understand how screen was useful sooner. Yes, but then it's not a useful default .screenrc, more of a

Re: Promote Screen? Include .screenrc!

David Marsh wrote: Yeah, I don't quite see how a screenrc would help either; I had the same problem. When I first tried it I couldn't see the point. Then I had problems with a machine constantly disconnecting me due to network problems, and out of frustration I tried screen to keep my

Re: Promote Screen? Include .screenrc!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Hi, Some years ago, I tried several Linux-Distros (Debian, SuSe, Fedora) and found the initial .screenrc-configuration-file quite, umm, minimalistic. (I don't know if that is still the case? Can anyone confirm?) I

Re: Open a window relative to the current

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kazuo Teramoto wrote: On Sun, Sep 21, 2008 at 3:53 PM, Micah Cowan [EMAIL PROTECTED] wrote: I'm not sure what you mean by this. The default for the screen command has always been to open the first available number (starting at 0); you can always

Re: Trunk Builds

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rich Healey wrote: Head just built and ran perfectly on OSX.. I'd been fighting with this on and off for sometime, but now I have my beloved Verticle Splits without resorting to ugly patches on the 4.0.2 tree. Glad to hear it! :) - -- Micah J.

Re: Patch to move and renumber windows, screen-4.0.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Adam wrote: Not having ever looked at the patch (sorry, no time) does it handle renumbering window in layouts correctly? Recall that a layout can have any number of differently numbered windows -- renumbering those such that it doesn't

Re: Patch to move and renumber windows, screen-4.0.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Hi, I've written a minor patch against 4.0.3 to add the ability to move windows right or left (up or down?) slot-by-slot (without using the :number UI), and also to renumber all active windows starting with 0,

Re: query current window title to stdout?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Parson wrote: I've got a user that wants to be able to, with a single command, rename the title for the current window when he edits a file to the name of the file he is editing. What I've come up with is a bash function: svim () {

Re: query current window title to stdout?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Micah Cowan wrote: However, you might take advantage of the special Dynamic Titles feature. Whoops! No, DON'T DO THAT. I forgot that the SEARCH portion of the SEARCH|NAME syntax _must_ be seen on the prompt, and before the user starts typing input

Re: bug #23945

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 YONETANI Tomokazu wrote: Hi. After the fix to #23945 (cb9d14bd8a198447d20ccd4be848df679a3047d9) committed, the cursor temporarily displayed at the wrong place when I enter copy-mode and move the cursor while Copy mode - ... caption is displayed.

Re: Man-writing volunteers?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Adam wrote: 2008/8/8 Micah Cowan [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, what would _really_ help me out in getting the documentation ready for a 4.1.0 release, is if someone would step up to volunteer

Re: Man-writing volunteers?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Adam wrote: 2008/8/12 Micah Cowan [EMAIL PROTECTED]: Anyway, enough ranting... down to logistics. It seems simplest to me for you to have push access on git. For that, you'll need to register an account with Savannah (if you don't have

Re: Screen, xterm, initialization strings.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephane Chazelas wrote: On Sun, Aug 10, 2008 at 07:42:22PM -0700, Micah Cowan wrote: [...] I propose that screen not send the initialization string. Probably with a command-line option that specifies it should be sent (though, IMO it should

Re: exec .! filters seeing responses to query escape sequences

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Juergen Weigert wrote: On Aug 08, 08 18:52:53 -0700, Micah Cowan wrote: For consistency, one could also consider having screen swallow up mouse-tracking responses, and reissue them down only the ttys on which requests had been seen

Screen, xterm, initialization strings.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, the other day, I suddenly found that screen was no longer using the alternate screen buffer as it usually does. Worse, screen _thought_ it was operating under the alternate screen buffer, so left a dirty screen upon exit. Thinking it was a

Man-writing volunteers?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, what would _really_ help me out in getting the documentation ready for a 4.1.0 release, is if someone would step up to volunteer to maintain the man page. The first step would be to ensure that the man page is in-step with the Texinfo manual;

Mouse-support with exec filters

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephane Chazelas wrote: On Fri, Aug 08, 2008 at 12:07:20PM -0700, Micah Cowan wrote: [...] Of course, if you'd like to hurry up the process, feel free to submit patches against the bugs that are left, so we can finish it up. :) [...] Hi Micah

Re: Getting screen size into the env?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aaron Davies wrote: How do I get the screen size env vars set properly? Screen appears to be populating TERMCAP for me (correctly), as it's not defined when outside of screen, but does exist inside. There's nothing that ever sets env vars to the

Screen 4.0.3 @ GNU FTP (existing release)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 FYI, the 4.0.3 sources are now also available at ftp.gnu.org, in addition to the uni-erlangen.de site. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. GNU Maintainer: wget, screen, teseq http://micah.cowan.name/ -BEGIN

Re: [screen-devel] couple of mac building issues, patch for one

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Micah Cowan wrote: (My mailer is doing the quoting backwards again) Tom Scogland wrote: On Thu, Jun 26, 2008 at 12:26 PM, Micah Cowan [EMAIL PROTECTED] wrote: Tom Scogland wrote: Hi, I've been a screen user for a few years on linux, but when

Re: Two little features (and a bounty?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joe Zbiciak wrote: Micah, This may be a silly question, but how does screen decide that the attaching terminal supports capturing mouse events? It could be that nano says it's interested, but screen thinks they're not available. I'm no

Re: Two little features (and a bounty?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Trent W. Buck wrote: Would it be better to have screen remember if an enable sequence was sent, so that if I *later* do xterm -e screen -xRR the *new* xterm will also know about mousiness? (IIUC, currently the xterm has to be connected

Re: [screen-devel] Scripting Support for Screen

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Johannes Weiner wrote: The trend I would like to see is not just extending screen with a powerful language but reducing the C code where possible by this language. Sort of like it's done with emacs (only that emacs was probably written to this

Re: [screen-devel] Scripting Support for Screen

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Johannes Weiner wrote: Hi, Micah Cowan [EMAIL PROTECTED] writes: Micah Cowan wrote: To be honest, implementing a Screen within Emacs makes almost as much sense as giving Screen Emacs-like scriptability Come to think of it, that functionality

Re: Two little features (and a bounty?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Mahoney, System Admin wrote: On Thu, 24 Jul 2008, Tom Scogland wrote: What do you mean about the mouse? It already sends mouse codes through from a terminal... Using gnome-terminal under linux, to a FreeBSD 6.2 system. Mouse works. I

Re: Two little features (and a bounty?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (My Thunderbird screws up the quoting, yours appear deeper than mine.) Dan Mahoney, System Admin wrote: On Thu, 24 Jul 2008, Micah Cowan wrote: Perhaps he's referring to the fact that it won't work until the application requests mouse tracking

Re: Two little features (and a bounty?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Adam wrote: On Thu, 24 Jul 2008 16:43:24 -0700 Micah Cowan [EMAIL PROTECTED] wrote: I have been successfully using both Emacs and Vim under screen with mouse support. Both required configuration adjustments to make it happen. Can you

Re: Two little features (and a bounty?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Mahoney, System Admin wrote: On Thu, 24 Jul 2008, Micah Cowan wrote: Dan Mahoney, System Admin wrote: That's unlikely to be true. The applications on the other end of the SSH tunnel requested the click events, first (based on the TERM env

Re: format windowlist view with color.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bruce Edge wrote: I have a lot of stuff in my screen sessions. 30+ terminal sessions on a dozen or more machines. I've tries a lot of things to make it more readable at a glance, but it keeps coming back to wanting color to highlight sections of

  1   2   >