From: Steve Dondley <s@dondley.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Is there any possible way to automatically escape characters when executing an alias in zsh?
Date: Sat, 11 Sep 2021 23:02:14 -0400 [thread overview]
Message-ID: <8057d5df08dc6e28c914b4b3983c3ec3@dondley.com> (raw)
In-Reply-To: <CAH+w=7ZFTm7DZ3d-yzqj7820hz0FtAK6k9QTcScAbN3_sMzokg@mail.gmail.com>
> See for example url-quote-magic. That does the typing for you, and
> you can see what it did to make sure it didn't do anything wrong.
> PWS's solution (and even my edit thereof) change the input at a time
> and place where it's too late for you to fix anything that's awry.
I can't think of a scenario off the top of my head but I'm not saying
you're wrong. Yes, it's hacky. However, issuing a bad command to TW is
not some mission critical problem that can't be easily reversed. Doing
the risk/reward calculus, it seems to have far more upsides than
potential downs.
I wouldn't recommend this as an official part of the TW release, but
since this is just a hack for my own use and convenience, I see no harm
in deploying it.
> You're not understanding. Given that you said --
>> minor completions (none of which will ever contain special characters
>> that need to be escaped)
> -- taskwarrior-literal should work fine. As with PWS's suggestion,
> this kicks in when you press enter (accept-line), so all your
> completions are already out of the way,
OK, right.
and it only quotes things that
> need quoting. The difference is that it blindly quotes ANYTHING that
> might be interpreted by the shell, including filename globs, etc.
I have modified PWS' solution to this:
accept-with-quote() {
if [[ $BUFFER = (tasn|tast|ta|tat|tm|taa|tai|tau|task)' '* && $BUFFER
!= *\\* ]]; then
BUFFER=${BUFFER//\'/\\\'}
BUFFER=${BUFFER//\(/\\\(}
BUFFER=${BUFFER//\)/\\\)}
BUFFER=${BUFFER//\&/\\\&}
fi
}
This doesn't look nearly as elegant as your solution. But I can (mostly)
understand it and modify it myself, which is probably more important for
a zsh newb like me.
But huge thanks for your time and input. I enjoying kicking the ball
around on this stuff. Helps me learn.
next prev parent reply other threads:[~2021-09-12 3:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 18:41 Steve Dondley
2021-09-11 19:00 ` zzapper
2021-09-11 19:16 ` Peter Stephenson
2021-09-11 19:28 ` Peter Stephenson
2021-09-11 20:45 ` Steve Dondley
2021-09-11 20:53 ` Peter Stephenson
2021-09-11 21:01 ` Steve Dondley
2021-09-11 22:39 ` Lawrence Velázquez
2021-09-11 23:15 ` Steve Dondley
2021-09-12 0:23 ` Bart Schaefer
2021-09-12 1:27 ` Steve Dondley
2021-09-12 2:26 ` Bart Schaefer
2021-09-12 3:02 ` Steve Dondley [this message]
2021-09-11 23:17 ` Bart Schaefer
2021-09-11 23:33 ` Steve Dondley
2021-09-12 3:33 ` Ray Andrews
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8057d5df08dc6e28c914b4b3983c3ec3@dondley.com \
--to=s@dondley.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).