On Tue, Dec 3, 2024 at 10:20 AM Chet Ramey wrote:
>
> On 12/2/24 7:29 PM, Keith Thompson wrote:
> > OK, that explains the problem, and I have a workaround.
> >
> > (Background: I have a personal tool that uses "foo:bar" syntax for
> > some of its arguments. I've modified the tool to use "foo/bar
>
On 11/27/24 10:54 PM, David Moberg wrote:
Yes, if seems like the way to do this in bash. It's unfortunate because
doing it with a binding is more elegant as it avoids polluting the terminal
output and shell history.
You don't have to put anything in the history you don't want to. If you
don't
On 12/2/24 10:52 PM, HP Prototyping wrote:
I am facing unexpected behaviour from the command 'set' from any newly
opened terminal window to access the shell prompt of my "Linux Mint" system.
I was expecting to see only the content of environment variables (as
always), But, I discovered a pretty
On 12/2/24 7:29 PM, Keith Thompson wrote:
OK, that explains the problem, and I have a workaround.
(Background: I have a personal tool that uses "foo:bar" syntax for
some of its arguments. I've modified the tool to use "foo/bar
instead.)
An easier workaround might have been removing `:' from CO
set without args displays also set functions
set say from .bashrc or .profile / .bash_profile
u may wanna have a detailed look at compgen to display types of stuff
On Tue, Dec 3, 2024, 3:38 PM HP Prototyping
wrote:
> Hi,
>
> I am contacting you about something I worry about while being taken in
