From: Paul Seyfert <pseyfert@mathphys.fsk.uni-heidelberg.de>
To: zsh workers <zsh-workers@zsh.org>
Subject: feature request: proposed completion highlightable
Date: Mon, 23 May 2016 19:41:14 +0200 [thread overview]
Message-ID: <574340BA.3080406@mathphys.fsk.uni-heidelberg.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
Hi,
zsh's correction suggestions can be hard to proofread e.g. when a long
path is changed only in a single letter romewhere in the middle.
So I was wondering if zsh-syntax-highlighting can be used to highlight
the suggestion (maybe boldfacing the differences).
I suggested this to zsh-syntax-highlighting
[OP: https://github.com/zsh-users/zsh-syntax-highlighting/issues/323]
but this can not be fixed there
(quoting danielshahaf's comment)
> In short: zsh itself does not make this possible at the moment:
> `spckword()` (a C function) prints the prompt by the equivalent of `print
> -rP -- $SPROMPT`, and there doesn't seem to be any prompt escape that
> could be used to manipulate %r and %R. I suggest that you ask zsh
> upstream to replace $SPROMPT by something smarter (e.g., converting the
> parameter to a zstyle would do, since then the style could be set with
> `zstyle -e`; or if there were a precorrect() hook, and you could write a
> hook that hardcodes $SPROMPT to a value that depends on the current
> values of %r and %R (using `print -rP %r` to get the value)).
>
> In any case, all this stuff happens outside zle, and there's a chance
> that it'll turn out to be out of scope for z-sy-h. (But let's keep this
> issue open for now)
Is it possible to address highlighting of proposed corrections from the
zsh side?
Thanks,
Paul
[-- Attachment #2: screenshot.png --]
[-- Type: image/png, Size: 9287 bytes --]
reply other threads:[~2016-05-23 18:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=574340BA.3080406@mathphys.fsk.uni-heidelberg.de \
--to=pseyfert@mathphys.fsk.uni-heidelberg.de \
--cc=zsh-workers@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).