multi-gnome-terminal alternative

Hello,

this one:

PS1='\[\033]0;$NICKNAME:\w\007\]\[\033[40;1;37m\]$NICKNAME>\[\033[0;m\] '

Jerome

Jhair Tocancipa Triana wrote:
> Jerome BENOIT writes:
>
>> Why my escape sequence which works fine on xterm does not work with
>> gnome-terminal ?
>
> Which escape sequence are you using?
>

--
Jerome BENOIT
jgmbenoit_at_mailsnare_dot_net

--

Roberto C. Sanchez wrote:
> Naturally, since he provided *zero* substantiation for his position (if
> you could even call it that), I asked if he had in fact used it. Now, I
> don't consider that bouncing email around. He did not provide a single
> point why gnome-terminal was unsuitable, so I'd like to see at least
> one.

It appears you didn't read the whole thread (one's mentioned ;-).

> BTW, I never claimed that gnome-terminal was a even a passable clone of
> xterm. Jerome wanted a possible substitude for multi-gnome-terminal. I
> figured the killer feature for him was multiple terminals, thus I
> recommended gnome-terminal.

>> (Your webpage doesn't work very well with Opera ;-)
>>=20
> Care to provide a screenshot? I test in Opera on Mac OS X and Linux
> and it looks no different than in Firefox.

(Opera 8.52)

ftp://invisible-island.net/temp/MenuProblem.png

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

--

Roberto C. Sanchez wrote:
> I'd be ineterested to learn more. I have been using gnome-terminal
> nearly every day since I started using Debian in late 2002. I have had
> very few issues with gnome-terminal.

>From what I read on google, you're an end-user of gnome-terminal, and
don't have any experience writing portable applications that use
terminals. End users have a different perspective: it's colorful, etc.
We don't argue about that.

A good place to start learning would be by reading bug reports for
gnome-terminal (some are older than your cited experience, but each
release of gnome-terminal produces new and interesting bugs).

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

--

On Wednesday 03 January 2007 10:32, Kamaraju Kusumanchi wrote:
> On Wednesday 03 January 2007 10:21, Sven Arvidsson wrote:
> > On Tue, 2007-01-02 at 14:02 -0500, Kamaraju Kusumanchi wrote:
> > > I really miss one feature from all these applications. I would like
> > > to have two terminals open side by side. All the input goes to one
> > > terminal, all the output (and errors if there are any) comes up in
> > > the second terminal. Clicking on a command in the first window should
> > > execute the command again. The whole thing looks similar to MATLAB's
> > > interface.
> > >
> > > Is there any terminal emulator which provides this kind of facility?
> >
> > You don't need a special program for that do you?
> >
> > echo helloworld &> /dev/pts/1
> >
> > This will redirect output, both normal and error messages from one
> > terminal to another. You can list the terminals and their TTY you have
> > open by typing "w".
>
> That is pretty cool to know. Thanks. But this requires
> appending "&> /dev/pts/1" to each and every command. Can this be done in
> some configuration file so that it works for each and every command?

You can rig something pretty quickly like this:

1. Open two terminals.
2. In the "output" terminal, run 'ps' to find out the shell pid.
3. Use lsof -p to find out the pts that the pid is using.
4. In the "input" terminal, run bash &> /dev/pts/xxx to start a shell and
redirect everything to the "output" terminal.

If you want typed commands to be also echoed on the "input" terminal, you
might have to fiddle with the stty settings.

--
Wesley J. Landaker
OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2

Kamaraju Kusumanchi writes:
> That is pretty cool to know. Thanks. But this requires appending "&>
> /dev/pts/1" to each and every command. Can this be done in some
> configuration file so that it works for each and every command?

Can't you just do something like:

exec >& /dev/pts/XXX

in the parent shell?

that basically changes the _shell's_ stdout and stderr to go to
/dev/pts/XXX.

Warning: _all_ output will be redirected, including prompts and the
"output" from command-line editing when you enter commands. However it
doesn't redirect the built-in echoing when you're not in bash's
command-line editing mode (you can turn off command-line editing by
doing "set +o emacs" in bash).

-Miles

--
Americans are broad-minded people. They'll accept the fact that a person can
be an alcoholic, a dope fiend, a wife beater, and even a newspaperman, but if a
man doesn't drive, there is something wrong with him. -- Art Buchwald

--