It seems that tmux is more clever than I am.
I open a new window (running bash). Therein, I run emacs -Q -f ielm.
At this point, tmux says the title is "emacs". Good! Now, I attempt to
have emacs set the window title to something more meaningful than
"emacs", such as the name of the file being
t...@cybersource.com.au (Trent W. Buck) writes:
> But: confusion! There is no "just one app" layout in tmux! My first
> guess is that there must be some way to move apps out of the current
> window (without killing them), such that "just one app" is simply to
> m
While I use Emacs-style bindings in Emacs and libreadline, I also use
a handful of vi-style bindings in screen, ed, less, w3m, etc.
It's cognitively dissonant for me to type, say, G in tmux's copy mode
and have nothing happen. I expect to be taken to the bottom of the
scrollback, and the confusio
"Levesque, Jean-Yves" writes:
> I am using mrxvt and I like to set different backgrounds depending on
> the window. However, this also does not work inside tmux where it
> works within screen. I am using mrxvtset.pl -pixmap xxx.xpm but
> nothing happens.
To answer that, we need to understand mrxv
Micah Cowan writes:
> I added the following line in my .tmux.conf:
>
> if 'test "$(tput colors)" = "256"' 'set -g default-terminal screen-256color'
When I investigated such an approach (for Screen instead of tmux), I
rejected it because one can create a screen on an eight-bit terminal
(e.g. xter
Being accustomed to xmonad's layout model, I find the tmux one a little
confusing. In xmonad (at least as _I_ use it), one has a set of apps[0]
open, and these are automatically tiled according to some layout
heuristic[1], such as "divide apps equally, side-by-side".
However, in xmonad, an app mi
Nicholas Marriott writes:
> OpenBSD is the primary repository at the moment because it is easier
> for me, SF is sync'd up fairly often by tcunha.
Do you have any plans to switch to a different VCS (e.g. git, svn) for
the primary repo?
--
Because screen doesn't implement -c like a normal shell, I can't use it
as my login shell without breaking scp(1) and suchlike. Thus for some
time I've had this in my .bash_profile:
## The naive "chsh -s /usr/bin/screen" breaks scp (and other things).
## Have sh start screen automatically
"Levesque, Jean-Yves" writes:
> I know this can probably not be done by default but is this possible
> for instance by using the terminal overrides strings? What I would
> like to do is to black on white for window 1 and blue on yellow for window
You may wish to play with tput. For example, in
AIUI tmux won't implement screen's support for serial ttys.
What, then, do tmux users do for these?
screen /dev/pts/4
screen /dev/ttyS0 38400
screen /dev/ttyUSB0 115200
I tried minicom yesterday, and it's bloody confusing. I couldn't even
work out how to make it use /dev/ttyS0 instea
[I'm playing catch-up in the archives again...]
Nicholas Marriott writes:
> On Wed, Feb 10, 2010 at 03:01:18PM -0800, Robin Lee Powell wrote:
>> A friend of mine has "per-pane status lines" as a requirement before
>> he starts using tmux; then you could title each pane appropriately.
>> Been mea
Nicholas Marriott writes:
> On Sun, Feb 14, 2010 at 01:22:02PM +1100, Trent W. Buck wrote:
>> Having said that, I'm haven't worked out how to make "setw -g
>> remain-on-exit on" only apply when the application returns a non-zero
>> exit status (the
clemens fischer writes:
> which of emacs/xemacs do you prefer?
I, and most of Freenode's #emacs denizens, use GNU Emacs. XEmacs seems
to mostly be restricted to those who started with Xemacs 19 rather than
previous or subsequent generations.
> I guess the subject says it all. My Emacs fu is r
Nicholas Marriott writes:
> Yeah we need to set the environment properly for job commands, there
> is an XXX in job.c for it.
Normally the environment is inherited from the parent process, but I see
you're using execle and explicitly passing an environment. Why?
Wouldn't it be simpler to tell
Nicholas Marriott wrote:
> What's the problem? tmux works the same way.
I was really just mentioning ~M~. as a workaround (for the ssh case).
Having said that, I'm haven't worked out how to make "setw -g
remain-on-exit on" only apply when the application returns a non-zero
exit status (the "onerr
[Going through the list's archives via gmane...]
Using tmux 1.1, I still get this kind of behaviour. The contrived
example I used was
1. start tmux
2. ^B%
3. for i in {1..99}; do dmesg; done
4. ^Bo (is ignored for a long time)
I'm still using GNU Screen, with a remote screen
16 matches
Mail list logo