please .. how what .. ?
On Thu, Jan 9, 2025, 11:15 PM Wiley Young wrote:
> On Wed, 8 Jan 2025 08:44:06 +1000,
> Martin D Kealey wrote:
>
> > I invite anyone to provide an example of how
>
> If the documentation changes at all, I think just a "See also..." might be
> enough.
>
> Wuley
>
i found it working if i $key in (( , not just '[key]'
i dunno i look for cmds to make em work ..
On Tue, Dec 31, 2024, 6:15 PM Chet Ramey wrote:
> On 12/29/24 4:34 PM, Lawrence Velázquez wrote:
>
> > I'm aware of the pitfalls described therein, and more. I don't
> > think anyone thinks multipl
https://lists.gnu.org/archive/html/help-bash/2022-08/msg00021.html
On Wed, Dec 25, 2024, 2:37 PM Zachary Santer wrote:
> On Tue, Dec 24, 2024 at 7:51 PM Lawrence Velázquez wrote:
> >
> > On Tue, Dec 24, 2024, at 12:10 PM, Zachary Santer wrote:
> > > Some other nonsense real quick:
> > >
> > > z
were my wrong assumptations .. sry .. peace ..
On Wed, Dec 18, 2024, 10:57 PM Kaz Kylheku wrote:
> On 2024-12-18 13:46, microsuxxor wrote:
> > try
> >
> > p=$$ ; while sleep 1 ; do kill -USR1 "$p" ; done &
>
> That's not necessary; my existin
On Wed, Dec 18, 2024, 10:40 PM Kaz Kylheku wrote:
> On 2024-12-18 12:48, Chet Ramey wrote:
> > On 12/18/24 1:27 PM, Kaz Kylheku wrote:
> >
> >> What remains is the question why I somehow cannot get my
> >> stuff to work with a different signal like SIGUSR1 or SIGVTALRM.
> >>
> >> Bash will not ta
i made smth with reserved line for some chat ..
On Wed, Dec 18, 2024, 8:18 PM Kaz Kylheku wrote:
> On 2024-12-18 11:02, microsuxxor wrote:
> > post ur code for review , if u want ..
>
> It's BSD-licensed freeware: https://www.kylheku.com/cgit/basta/about/
>
post ur code for review , if u want ..
On Wed, Dec 18, 2024, 7:28 PM Kaz Kylheku wrote:
> On 2024-12-18 06:58, Chet Ramey wrote:
> >> With signals other than SIGALRM, the code has to be careful; if it
> >> ever happens that the signal is delivered without the trap being
> >> in place, Bash will
history -s dummy args
On Wed, Dec 18, 2024, 4:58 PM Dale R. Worley wrote:
> Chet Ramey writes:
> > On 12/17/24 5:19 PM, Dale R. Worley wrote:
> > but it's tough to use programatically: How would
> >> you code a function for use in scripts that adds an entry "foo bar baz"
> >> to the history
a COMMAND is a WORD
says somewhere .. somewhere ..
On Thu, Dec 12, 2024, 5:56 PM Mike Jonkmans wrote:
> On Thu, Dec 12, 2024 at 03:56:52AM -0500, Lawrence Velázquez wrote:
> > On Thu, Dec 12, 2024, at 2:01 AM, Mike Jonkmans wrote:
> > > Yes, the posix grammar doesn't allow it.
> > > But it is no
a simple command is a pipeline
On Tue, Dec 10, 2024, 9:44 AM Andreas Schwab wrote:
> On Dez 10 2024, Mike Jonkmans wrote:
>
> > With 'if false... fi | true' there are two pipelines:
> > 1) false
> > 2) (compound command) if | true
>
> There is only one pipeline, consisting of two commands.
>
> -
maybe internal cmds dont statisfy it a pipestatus worthy
On Tue, Dec 10, 2024, 9:29 AM Ulrich Müller wrote:
> > On Mon, 09 Dec 2024, Mike Jonkmans wrote:
>
> >> Why is `if false; then :; fi' not a pipeline? It is a command, and the
> >> components of a pipeline are commands.
>
> > It is a p
the | true is the.last pipe
while witbout , its.one cmd less
the | true is $pipestatus[1][*]
On Tue, Dec 10, 2024, 4:31 AM Dale R. Worley wrote:
> Andreas Schwab writes:
> >> But the PIPESTATUS refers to the 'false' pipeline:
> >> $ if false; then :; fi; echo ${PIPESTATUS[*]}
> >> 1
>
its a pass return codes passthru question ..
.. id like it passthru too , that it returns the upper cmds return codes ..
On Mon, Dec 9, 2024, 6:22 PM Ulrich Müller wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: x86_64-p
maybe its easier to read -r -a some
On Thu, Dec 5, 2024, 6:13 PM microsuxxor wrote:
> ~ $ eval set -- "$( IFS=' ' ; printf %q\ 1 two ' th r ee ' '$( four >&2
> )' )" ; printf -- -%s-\\t "$@" ; printf \\n
> -1- -two-
~ $ eval set -- "$( IFS=' ' ; printf %q\ 1 two ' th r ee ' '$( four >&2 )'
)" ; printf -- -%s-\\t "$@" ; printf \\n
-1- -two- - th r ee - -$( four >&2 )-
On Thu, Dec 5, 2024, 5:54 PM microsuxxor wrote:
> ~ $ IFS=&#
~ $ IFS=' ' ; declare -a "a=( $( printf %q\ 1 two ' th r ee ' '$( four >&2
)' ) )" ; set -- "${a[@]}" ; printf -- -%s-\ \ "$@" ; printf \\n
-1- -two- - th r ee - -$( four >&2 )-
On Thu, Dec 5, 2024, 5:48 PM Chet Ramey wrote:
> On 12/5/24 9:41 AM, Clark Wang wrote:
> > It would be easier to
for it
On Thu, Dec 5, 2024, 3:42 PM Clark Wang wrote:
> It would be easier to manipulate positional params if we can write like
> `printf -v 1`.
>
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
On Sat, Nov 30, 2024, 2:05 AM Dan Jacobson wrote:
> $ history
> is nice, but what if you want to have it read from a different file?
> $ help history
> says
> If FILENAME is given, it is used as the history file. Otherwise,
> if HISTFILE has a value, that is used, else ~/.bash_history.
>
19 matches
Mail list logo
