From: ZyX <kp-pav@yandex.ru>
To: Bart Schaefer <schaefer@brasslantern.com>,
"zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: ANSI bg colour outside of prompt area
Date: Mon, 23 Feb 2015 15:34:03 +0300 [thread overview]
Message-ID: <4975571424694843@web14h.yandex.ru> (raw)
In-Reply-To: <150222172204.ZM19090@torch.brasslantern.com>
23.02.2015, 04:23, "Bart Schaefer" <schaefer@brasslantern.com>:
> On Feb 23, 12:55am, ZyX wrote:
> } Subject: Re: ANSI bg colour outside of prompt area
> }
> } > That's intentional so that a misbehaving program can't e.g. cause your
> } > prompt to become invisible by changing the background to the same color
> } > as your prompt foreground.
> }
> } I am wondering whether same thing may apply to \C-n (0x0E, Shift Out).
> } It is the second annoying thing that may garble everything, much more
> } annoying since it changes the view of most characters and I have to
> } type either `echo $'\ec'` or `echo $'\c-o'`.
> }
> } I mean, whether it makes sense to output \C-o to drop SO mode by
> } default just like it is done currently with colors.
>
> Hrm. The Lock Shift feature to chose character sets is a lot less common,
> the prompt code would actually have to check that the G0 capability is
> present in the terminal definition, etc. I'm not personally familiar with
> the terminal handling code in prompt.c ... on brief examiniation I can't
> even find where it's emitting color reset and clear-screen.
>
> Still, there's no reason you can't put $'%{\CO%}' at the front of $PS1.
> Or putting that in $PROMPT_EOL_MARK might work as well.
I have actually put this into `precmd_functions` array. And am experiencing weird behavior since the time I put it: character set is not changing on SO ever since I started to emit \C-o in konsole.
I mean, I start a new terminal using konsole -e zsh -f and it does not change character set on `echo $'\C-n'`. Need to change to fbterm (framebuffer terminal) to see the switch; this one is not going to lock on \C-o mode.
next prev parent reply other threads:[~2015-02-23 12:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 13:23 junkcommander0
2015-02-22 16:52 ` Ray Andrews
2015-02-22 19:10 ` Bart Schaefer
2015-02-22 20:07 ` junkcommander0
2015-02-22 21:55 ` ZyX
2015-02-23 1:22 ` Bart Schaefer
2015-02-23 1:55 ` Vincent Lefevre
2015-02-23 12:34 ` ZyX [this message]
2015-02-22 23:10 ` Ray Andrews
2015-02-23 0:10 ` ZyX
2015-02-23 0:28 ` Kurtis Rader
2015-02-23 1:14 ` Bart Schaefer
2015-02-23 1:44 ` Kurtis Rader
2015-02-23 2:04 ` Vincent Lefevre
2015-02-23 2:18 ` Kurtis Rader
2015-02-23 3:41 ` Ray Andrews
2015-02-23 4:03 ` Kurtis Rader
2015-02-23 5:34 ` Ray Andrews
2015-02-23 4:14 ` Kurtis Rader
2015-02-23 5:49 ` Bart Schaefer
2015-02-23 9:46 ` Vincent Lefevre
2015-02-23 16:36 ` Bart Schaefer
2015-02-23 16:51 ` Ray Andrews
2015-02-24 2:53 ` Bart Schaefer
2015-02-24 3:49 ` junkcommander0
2015-02-24 4:33 ` Ray Andrews
2015-02-24 4:25 ` Ray Andrews
2015-02-24 8:36 ` Vincent Lefevre
2015-02-23 5:27 ` Bart Schaefer
2015-02-23 1:51 ` Vincent Lefevre
2015-02-23 0:55 ` Ray Andrews
2015-02-23 1:36 ` Vincent Lefevre
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=4975571424694843@web14h.yandex.ru \
--to=kp-pav@yandex.ru \
--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).