On Sat, Jul 12, 2025, at 8:51 PM, Robert Elz wrote:
> Date:Sat, 12 Jul 2025 18:52:55 -0400
> From:Zachary Santer
> Message-ID:
>
>
> | Same applies to parameter expansion syntax errors.
>
> The NetBSD shell used to do that (and POSIX even allows it), but
> it turns out
On Sun, Jul 13, 2025, at 4:53 PM, jason stein wrote:
> It's a history of all the paths we used with cd command, so it might be
> confusing due to legacy use of history, but it is a type of history.
Sure, in an abstract sense. However, in practice bash extensively
refers to the command history as
Address you points:
#1
VQ: With the exception of the file, this sounds nothing like the "history"
command, so using that word runs the risk of confusing users.
JS: It's a history of all the paths we used with cd command, so it might be
confusing due to legacy use of history, but it is a type of hi
*Patch*
>From eed27ce56dfccef103d51379215c38a8438ec998 Mon Sep 17 00:00:00 2001
From: Jason Stein
Date: Sun, 13 Jul 2025 11:08:24 -0700
Subject: [PATCH] Add dh (directory history) builtin
- Implement dh builtin for frequency-based directory navigation
- Add comprehensive test suite with run-dh,
*Per Lawrence **Velázquez*
Sending a new email to bug-bash@gnu.org. Original was sent to
help-bash@gnu-org which Lawrence indicated was the incorrect mailing list
(Thanks Lawrence).
Hey All,
I developed a new builtin and I was wondering what is the process for
getting it added to the official rel
> On Jul 13, 2025, at 3:58 PM, Lawrence Velázquez wrote:
>
> On Sun, Jul 13, 2025, at 3:17 PM, jason stein wrote:
>> *Pull Request:*
>> https://github.com/jstein916/bash/pull/1
>
> In general it's preferable to provide a patch directly (either inline
> or as an attachment), rather than requiring
On Sun, Jul 13, 2025, at 3:17 PM, jason stein wrote:
> *Pull Request:*
> https://github.com/jstein916/bash/pull/1
In general it's preferable to provide a patch directly (either inline
or as an attachment), rather than requiring prospective reviewers to
visit an external site.
> *What the command
Missed a comma…
On Mon, 14 Jul 2025, 03:43 Martin D Kealey, wrote
> an expression would be parsed and then when executed [COMMA] the
> expression itself - rather than the value resulting from evaluating it -
> could be assigned to a variable.
>
>
> Since when is removal of recursive evaluation being mooted?
>
Not by me, but if we're going down the path of parsing numeric expressions
at the same time as the surrounding shell commands, it would be useful to
have some sort of lambda assignment, so an expression would be parsed and
then when
Configuration Information [Automatically generated, do not change]:
Machine: aarch64
OS: darwin24.4.0
Compiler: clang
Compilation CFLAGS: -DSSH_SOURCE_BASHRC
-DDEFAULT_LOADABLE_BUILTINS_PATH='/opt/homebrew/lib/bash:/usr/local/lib/bash:/usr/lib/bash:/opt/local/lib/bash:/usr/pkg/lib/bash:/opt/pkg/lib
10 matches
Mail list logo
