From: Bart Schaefer <schaefer@brasslantern.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Sebastian Gniazdowski <sgniazdowski@gmail.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Feature request: italic style in region_highlight
Date: Mon, 30 Dec 2019 08:07:53 -0800 [thread overview]
Message-ID: <CAH+w=7atVBgGEQ0M919mKLzqrcJBHALgLcuKFQmyRYCad00JdQ@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMpBOD5XJOgjiOWYUJV4QaV2Fn9+PkgTCTMtArJ4GxJA8w@mail.gmail.com>
On Mon, Dec 30, 2019 at 2:17 AM Roman Perepelitsa
<roman.perepelitsa@gmail.com> wrote:
>
> Zsh sort of supports italicized text through "standout" attribute in
> ncurses. ncurses translates standout to italicized on some terminals
> and to negative image on others.
The way the "colors" function/array have dealt with similar issues is
to declare e.g color[grey]=${color[black]} ... however, the difference
between negative image and italic may be too drastic to alias that to
standout.
> When printing text, you can use `colors` from contrib to bypass
> ncurses. Confusingly enough, in `color` associative array the key for
> italicized text is "standout" (negative image goes by "reverse").
I believe the use of "standout" there comes from the xterm
documentation (circa the time the colors function was contributed, it
may have since been updated).
> zle_highlight=(default:standout standout_begin_code:'\e[3m'
> standout_stop_code:'\e[23m')
>
> fg_start_code and fg_end_code specify the prefix and the suffix of a
> single escape sequence. To avoid confusion, I've used begin/stop with
> standout. It's awkward, as the natural pairing would be start/stop and
> begin/end. Oh well.
Could use standout_enter/exit (or enter/end).
next prev parent reply other threads:[~2019-12-30 16:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 1:29 Sebastian Gniazdowski
2019-12-30 10:16 ` Roman Perepelitsa
2019-12-30 16:07 ` Bart Schaefer [this message]
2019-12-30 16:26 ` Roman Perepelitsa
2020-01-01 0:07 ` Bart Schaefer
2020-01-02 19:18 ` Oliver Kiddle
2020-01-02 19:45 ` Roman Perepelitsa
2020-01-03 2:30 ` Bart Schaefer
2020-01-03 20:28 ` Daniel Shahaf
2021-05-20 13:33 ` Marlon Richert
2021-05-25 16:38 ` Oliver Kiddle
2021-05-25 20:50 ` Marlon Richert
2021-05-25 20:56 ` Bart Schaefer
2021-05-27 8:04 ` Marlon Richert
2021-05-25 17:28 ` Bart Schaefer
2021-05-25 22:43 ` Oliver Kiddle
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='CAH+w=7atVBgGEQ0M919mKLzqrcJBHALgLcuKFQmyRYCad00JdQ@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=roman.perepelitsa@gmail.com \
--cc=sgniazdowski@gmail.com \
--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).