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
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 configuration:
~$ stty -a
speed 38400 baud
26 matches
Mail list logo
