On 6/7/22 10:17 AM, Gergely wrote:
On 6/7/22 15:49, Chet Ramey wrote:
On 6/7/22 7:57 AM, Gergely wrote:
Because you haven't forced bash to write outside its own address space or
corrupt another area on the stack. This is a resource exhaustion issue,
no more.
I did force it to write out of bou
On 6/8/22 5:06 PM, Luciano wrote:
Hi!
I had the terrible idea to set my EDITOR variable to something too
complex. I had to pass some options with whitespace to vim, so i decided
to use `eval`. I managed to get something working, but the way the
EDITOR variable is interpreted isn't consistent
to p
Hello,
I want to propose patch that provides PREEXEC_COMMAND var similar to
PROMPT_COMMAND.I believe that this patch is not first that you recieve
but I will try.
The patch is in attachment (I don’t trust gmail editor).
Regards,
Constantine
diff --git a/doc/bash.1 b/doc/bash.1
index 5af7d42..33ba
On Wed, Jun 08, 2022 at 05:49:52PM -0400, Greg Wooledge wrote:
>You could create a wrapper script, put it in your $HOME/bin/ directory
>(and make sure that's in PATH), and then set EDITOR to that wrapper.
>That should be much more reliable, especially if other programs also
>use $EDITOR (which t
On Thu, Jun 9, 2022, at 8:37 PM, Luciano wrote:
> By the way, git seems to interpret the EDITOR variable in a way
> consistent with C-x C-e, while the pass program as I said seems to just
> execute $EDITOR, like fc. I wonder if POSIX leaves room for
> interpretation here.
It does, insofar as it
