On Wed, Jun 08, 2022 at 06:06:51PM -0300, Luciano wrote:
> 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`. [...]
You could create a wrapper script, put it in your $HOME/bin/ directory
(an
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 provide an example, if one sets EDIT
At 2022-06-08T12:05:06-0500, mcmuffin6o wrote:
> In section 3.5.3 Shell Parameter Expansion:
>
> In the sixth paragraph it correctly states that "Bash tests for a
> parameter that is unset *or* null" when you use the colon. It later
> attempts to restate this but fails by saying "if the colon is
>
In section 3.5.3 Shell Parameter Expansion:
In the sixth paragraph it correctly states that "Bash tests for a parameter
that is unset *or* null" when you use the colon. It later attempts to
restate this but fails by saying "if the colon is included, the operator
tests for both parameter's existenc
