On 2025-02-03 18:14, microsuxx wrote:
i suggest u be some kinder ..
I have a long history on various Linux forums and always strive to
remain polite and respectful. However, I have a very low tolerance for
practices like top posting and responses that seem nonsensical or
dismissive. As some
On 2025-02-03 23:54, Greg Wooledge wrote:
We are talking about shtty.c
Read the code and figure it out yourself since your so smart.
Zeffie
To whom it may concern,
I wanted to bring to your attention that the bash-bug mailing list
messages are being marked as spam by our spam filtering. The debug
headers indicate an "Invalid DKIM signature" which appears to be causing
the posts to be flagged.
This is particularly concerning beca
Lawrence Velázquez,
To clarify, several points in your response appear to miss the mark on
the core issue of the bug report:
Focus on $BASH_VERSION:
While you argue about testing for $BASH_VERSION, this point isn’t
central to the bug report. The issue is about terminal reinitialization
in
On 2025-02-03 23:29, Lawrence Velázquez wrote:
On Mon, Feb 3, 2025, at 11:08 PM, Zeffie via Bug reports for the GNU
Bourne Again SHell wrote:
READ THE BUG REPORT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284513
Yes, let's.
The default FreeBSD bourne shell /bin/sh see
On 2025-02-03 23:52, Lawrence Velázquez wrote:
Unbelievable.
Yeah you are. Go read the code and walk away. Clearly you don't have any
more then trolling to contribute.
Zeffie
Thank you for taking the time to not review the FreeBSD bug report (Bug
284513) in full before responding. Your willingness to speculate on
behaviors without testing in the relevant environment is duly noted and
much appreciated.
Now, let’s break down the issues with your response:
1. `echo $
On 2025-02-03 22:19, microsuxx wrote:
~ $ p=~:~:~ ; declare -p p
declare --
p="/data/data/com.termux/files/home:/data/data/com.termux/files/home:/data/data/com.termux/files/home"
~ $ cp $( type -P bash ) sh
~ $ ./sh
sh-5.2$ x=~:~:~:
sh-5.2$ declare -p x
declare --
x="/data/data/com.termux/files
On 2025-02-03 22:53, Lawrence Velázquez wrote:
The bug report is about FreeBSD ash, not bash.
The bug report is about FreeBSD ash, not bash.
The bug report is about FreeBSD ash, not bash.
The bug report is about FreeBSD ash, not bash.
The bug report is about FreeBSD ash, not bash.
The bug report
To whom it may concern,
Bash has long maintained a legacy feature whereby, in interactive
sessions, a literal tilde (`~`) at the start of a `PATH` element (e.g.,
`~/bin`) is expanded to the user’s home directory at the time a command
is executed. While this behavior can sometimes “help” users
On 2025-02-03 20:11, Lawrence Velázquez wrote:
I'm sorry you didn't get the response you expected, and you're
free to express your disagreements, but as a guest here you've
been incredibly rude.
After two uncalled-for responses that have wasted my time, I must say
that this behavior is complet
Thank you for your thoughts. While I appreciate your perspective on DKIM
and spam filtering, I expect the list maintainers to handle these issues
properly. I've been running mail servers since the 1990s, so I
understand the complexities involved. Even if many messages on the list
aren’t signed
Please show the scenario where bash isn't preserving the ECHOCTL flag
if
it's present. The function you're modifying below changes the settings
in
a termios struct that holds the current terminal settings. If the
ECHOCTL
flag is set there, bash won't change it.
Further, the function you're mod
Hello,
This patch is submitted for consideration only. It addresses an issue in
sh‑mode where Bash fails to preserve the user-configured echoctl flag.
As described in [Bug
284513](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284513), the
default FreeBSD /bin/sh (which behaves similarly t
14 matches
Mail list logo
