On 2024-07-10 16:00:48 +0200, Nicolas George wrote:
> Greg Wooledge (12024-07-10):
> > You could -- but if you do so, you should definitely surround it with
> > a check for stdin being a terminal (test -t 0 or equivalent).
>
> Does bash execute .bashrc when it is not interactive?
Yes, it may exec
On 12/07/2024 10:56, Max Nikulin wrote:
I have a question opposite to the original one. Is it possible to
disable xon&xoff for bash prompt, but enable it while foreground
commands are running?
I do not mind to use forward search in readline history.
As to the original question, Emacs and Vim
On 11/07/2024 22:56, Greg Wooledge wrote:
On Thu, Jul 11, 2024 at 22:43:58 +0700, Max Nikulin wrote:
On 10/07/2024 20:55, Greg Wooledge wrote:
test -t 0 && stty -ixon
I have a question opposite to the original one. Is it possible to disable
xon&xoff for bash prompt, but enable it while
On Thu, Jul 11, 2024 at 22:43:58 +0700, Max Nikulin wrote:
> On 10/07/2024 20:55, Greg Wooledge wrote:
> > test -t 0 && stty -ixon
>
> I have a question opposite to the original one. Is it possible to disable
> xon&xoff for bash prompt, but enable it while foreground commands are
> running? S
On 10/07/2024 20:55, Greg Wooledge wrote:
test -t 0 && stty -ixon
I have a question opposite to the original one. Is it possible to
disable xon&xoff for bash prompt, but enable it while foreground
commands are running? Sometimes I use [Ctrl+s] to pause verbose output
of some tool. On th
songbird (12024-07-10):
> but for my own purposes i also like to do things for
> terminals when they open up (my session manager and the
> overall desktop will store multiple desktops and all of
> the terminals i have open in each of them when i ask it
> to).
This is absolutely legitimate.
Note
Greg Wooledge wrote:
...
> Sadly, the days of designing software to accomodate actual hardware
> terminals are quite far behind us.
true.
having been annoyed by the quit keys of Firefox i just
went and found the way to turn that off. been burned by
that one too many times and i'd still not l
On 7/10/24 21:18, Greg Wooledge wrote:
On Wed, Jul 10, 2024 at 21:01:41 -0400, e...@gmx.us wrote:
On 7/10/24 18:57, Greg Wooledge wrote:
On Wed, Jul 10, 2024 at 18:39:38 -0400, songbird wrote:
that is a strange choice of termination and i would
actually consider it a bug in rtorrent, ESC o
On Wed, Jul 10, 2024 at 21:01:41 -0400, e...@gmx.us wrote:
> On 7/10/24 18:57, Greg Wooledge wrote:
> > On Wed, Jul 10, 2024 at 18:39:38 -0400, songbird wrote:
> > >that is a strange choice of termination and i would
> > > actually consider it a bug in rtorrent, ESC or Ctrl-C
> > > should work
On 7/10/24 18:57, Greg Wooledge wrote:
On Wed, Jul 10, 2024 at 18:39:38 -0400, songbird wrote:
that is a strange choice of termination and i would
actually consider it a bug in rtorrent, ESC or Ctrl-C
should work for that purpose.
Emacs and bash both use Ctrl-S to do stuff, and in both case
Nicolas George wrote:
> Greg Wooledge (12024-07-10):
>> There are many legitimate or semi-legitimate situations where a .bashrc
>> file might be read by a shell that's not running inside a terminal.
>>
>> One of them is if someone chooses to dot in ~/.profile from their
>> ~/.xsession file, or som
On Wed, Jul 10, 2024 at 18:39:38 -0400, songbird wrote:
> Franco Martelli wrote:
> > Hi everybody,
> >
> > I sometime use "rtorrent" (apt show rtorrent) to download isos and other
> > big files. It happens that when I had to quit rtorrent by press Ctrl-Q I
> > cannot because the key combination C
Franco Martelli wrote:
> Hi everybody,
>
> I sometime use "rtorrent" (apt show rtorrent) to download isos and other
> big files. It happens that when I had to quit rtorrent by press Ctrl-Q I
> cannot because the key combination Ctrl-Q is trapped by the console due
> to "stty" default configurati
To summarize:
* When configuring your shell dot files, make sure you DON'T write
anything to stdout, unless you have verified that stdout is a
terminal. Otherwise, it can mess up ssh sessions and other things.
* Likewise, DON'T run stty, or other terminal manipulation commands,
unless
On Wed, Jul 10, 2024 at 05:08:20PM +0200, Nicolas George wrote:
> Greg Wooledge (12024-07-10):
[...]
> > (I won't even bother explaining because you CLEARLY know better than I
> > do about all topics. Enjoy your day.)
>
> The risk of passive-aggressive like that is that you risk to be right.
F
On 10/07/24 at 16:45, Greg Wooledge wrote:
test -t 0 && stty -ixon
That should be safe to add to your .bashrc.
...
One of them is if someone chooses to dot in ~/.profile from their
~/.xsession file, or something analogous to it. Or perhaps their
operating system does this automatically in
Greg Wooledge (12024-07-10):
> hobbit:~$ echo 'echo I AM BASHRC' >> .bashrc
> hobbit:~$ ssh localhost date
> greg@localhost's password:
> I AM BASHRC
> Wed Jul 10 11:01:00 EDT 2024
> hobbit:~$
~ $ echo "I am in zshrc" >> .zshrc
~ $ ssh localhost date
~ $ ssh localhost date
Wed Jul 10 17:05:01
On Wed, Jul 10, 2024 at 16:50:38 +0200, Nicolas George wrote:
> Greg Wooledge (12024-07-10):
> > There are many legitimate or semi-legitimate situations where a .bashrc
> > file might be read by a shell that's not running inside a terminal.
> >
> > One of them is if someone chooses to dot in ~/.pr
Greg Wooledge (12024-07-10):
> There are many legitimate or semi-legitimate situations where a .bashrc
> file might be read by a shell that's not running inside a terminal.
>
> One of them is if someone chooses to dot in ~/.profile from their
> ~/.xsession file, or something analogous to it. Or p
Franco Martelli wrote:
> Hi everybody,
>
> I sometime use "rtorrent" (apt show rtorrent) to download isos and other big
> files. It happens that when I had to quit rtorrent by press Ctrl-Q I cannot
> because the key combination Ctrl-Q is trapped by the console due to "stty"
> default configuratio
On Wed, Jul 10, 2024 at 16:27:16 +0200, Nicolas George wrote:
> David Wright (12024-07-10):
> > Someone might source .bashrc from a binary in order to
> > access functions that are defined within it.
>
> That would be shooting oneself in the foot. No need to cater for them.
There are many legitim
David Wright (12024-07-10):
> Someone might source .bashrc from a binary in order to
> access functions that are defined within it.
That would be shooting oneself in the foot. No need to cater for them.
Regards,
--
Nicolas George
On Wed 10 Jul 2024 at 16:00:48 (+0200), Nicolas George wrote:
> Greg Wooledge (12024-07-10):
> > You could -- but if you do so, you should definitely surround it with
> > a check for stdin being a terminal (test -t 0 or equivalent).
>
> Does bash execute .bashrc when it is not interactive?
Someon
Greg Wooledge (12024-07-10):
> You could -- but if you do so, you should definitely surround it with
> a check for stdin being a terminal (test -t 0 or equivalent).
Does bash execute .bashrc when it is not interactive?
Does bash think it is interactive when its input is not a tty?
Regards,
--
On Wed, Jul 10, 2024 at 15:49:59 +0200, Franco Martelli wrote:
> ~$ stty start undef
>
> So, is there a way to permanently set "start" as "undef"? Maybe under /etc/?
> Should I put this command in .bashrc?
You could -- but if you do so, you should definitely surround it with
a check for stdin bei
On Thu, Oct 12, 2006 at 04:39:20PM -0400, T wrote:
> Hi
>
> In my script, I always use 'stty sane' to set my tty to a sane stage, after
> temporally changing any tty attributes.
>
> But for recent month or two, my BS key often stop working, only today did I
> finally track it down to the 'stty s
$ stty sane
$ asdsf^H^H^H
I.e., my BS key is producing ^H instead of erasing previous letter afterward.
So what should I do? I still like to use 'stty sane' to reset my tty, and I
still want my BS key to be configured as ^H, instead of something else.
stty erase ^H, perhaps?
regards,
--
On Thu, Jun 08, 2000 at 12:36:41PM +0100, David Wright wrote:
> Quoting Johann Spies ([EMAIL PROTECTED]):
> > If I use stty to configure a serial port, will the settings be the
> > same after a reboot? Or do I have to put the settings in some init
> > file similar to /etc/rc.boot/0setserial.
>
>
Quoting Johann Spies ([EMAIL PROTECTED]):
> If I use stty to configure a serial port, will the settings be the
> same after a reboot? Or do I have to put the settings in some init
> file similar to /etc/rc.boot/0setserial.
While my previous reply might have been correct for slink,
there appears t
Quoting Johann Spies ([EMAIL PROTECTED]):
> If I use stty to configure a serial port, will the settings be the
> same after a reboot? Or do I have to put the settings in some init
> file similar to /etc/rc.boot/0setserial.
I think you'll find that even reloading the serial module will
reset the p
On Mon, Jan 25, 1999 at 04:48:25PM +, Nidge Jones wrote:
> > Do you have $TERMINFO set perhaps,
> AH! Now were getting somehwere. Everyone keeps mentioning TERMINFO and
> TERMCAP. But how do I know if mines OK. how do I test the paths etc.
Okay, at your shell, just type
echo $TERMINFO
you sh
Nidge Jones <[EMAIL PROTECTED]> writes:
> > (It shouldn't ask if you hadn't changed the files, but due to bugs
> > it does sometimes.)
> Some nice guy on #debian/IRC (remco I think) got me to do a checksum on
> /etc/terminfo/v/vt100 yesterday, and he say the result was the same as his..
> and his
Nidge Jones <[EMAIL PROTECTED]> writes:
>However, if I then Maximise the CRT window (or resize by dragging the edge
>of the box), to get a bigger display, Linux still shows the out put as
>80x25?
I'll try to explain how this thing should work. (Correct me if I'm
wrong, anyone, this is mostly from
> Nidge: I don't know why yours is hosed, but since it's worked for so many
> other people, and you mentioned problems with joe as well, it's probably
> something you hosed yourself.
Yes but the 'upgrade' went OK with no errors, so how can that be ?
I don't want to get into a battle on who's faul
Nathan E Norman <[EMAIL PROTECTED]> wrote:
> "Hey, my system's all FUBAR and I'm pissed off. You jerks at Debian
> hosed it up - *I* didn't do it. Fix it now or I'll really be pissed"
No not at all. Debian 1.3.1 is/was the dogs parts, I loved/love it. I
have spent years with Linux now, and thr
On Sun, Jan 24, 1999 at 08:11:22PM -0600, Nathan E Norman wrote:
> Sorry my tech support isn't quite up to your expectations. I'll be sure
> to return your money.
Indeed.
Nidge: I don't know why yours is hosed, but since it's worked for so many
other people, and you mentioned problems with joe a
On Sun, 24 Jan 1999, Nidge Jones wrote:
[ snip ]
: The man at the garage doesn't say that everyone else's car is OK does he
: when you take yours there cus it's fucked..., he locates and solves the
: problem?
:
: So why have a million people mailed me with "mine's OK" ? Please stop
: send
On Mon, Jan 25, 1999 at 12:47:04AM +1100, Hamish Moffatt wrote:
> Same here. I just maximised my CRT window (I'm using 2.3 right now)
> and mutt adjusted correctly. And same when I restored it.
Yes I know this should happen. You can have a million people say its OK
here, indeed mine used to be un
On Sat, Jan 23, 1999 at 11:34:44AM -0600, Nathan E Norman wrote:
> On Sat, 23 Jan 1999, Nidge Jones wrote:
> : I use CRT from windows from time to time to access my Debian 2.0 install.
>
> : However, if I then Maximise the CRT window (or resize by dragging the edge
> : of the box), to get a big
On Sat, Jan 23, 1999 at 11:34:44AM -0600, Nathan E Norman wrote:
> Sounds like something is AFU ... I've used CRT for a few years now, with
> bo, hamm, slink, and potato, and I've never seen that problem.
Humm ! Well I have it, and I need to cure it :(
> What's your terminal setting in CRT? I
On Sat, 23 Jan 1999, Nidge Jones wrote:
:
: I use CRT from windows from time to time to access my Debian 2.0 install.
[ snip ]
: However, if I then Maximise the CRT window (or resize by dragging the edge
: of the box), to get a bigger display, Linux still shows the out put as
: 80x25?
:
> By the way, having 7 data bits and 2 stop bits should be equivalent to
> having 8 data bits without parity generation and 1 stop bit. This is
> because the data bits are sent least significant bit first, and a stop
> bit is the same as a zero data bit.
> ...
> Steve Preston ([EMAIL PROTECTED])
> Dale Scheetz <[EMAIL PROTECTED]> writes:
> I can point setserial at a particular port, but can't seem to tell it to
> set the stop bits to two.
By the way, having 7 data bits and 2 stop bits should be equivalent to
having 8 data bits without parity generation and 1 stop bit. This is
becaus
Dale Scheetz <[EMAIL PROTECTED]> writes:
> I can point setserial at a particular port, but can't seem to tell it to
> set the stop bits to two.
> I can tell stty to set the stop bits, but can only seem to use it while on
> the tty in question. Is there any way to point stty at the port I want
> ch
44 matches
Mail list logo
