From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28810 invoked by alias); 23 Feb 2015 12:40:35 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 19908 Received: (qmail 20172 invoked from network); 23 Feb 2015 12:40:32 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_FSL_HELO_BARE_IP_2 autolearn=ham version=3.3.2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1424694844; bh=37lqzMZPpyFmz5BWjCuj3irW2fQzF5DVlwGpc85H1Hk=; h=From:To:In-Reply-To:References:Subject:Date; b=kdpgeSWli3ioCpW2cvIFTswQxBuDrOA5bS1dgVwspKDCGI6qLyv+OV42FW/3jXG2R eo44m148RS4Zz/32wMavTErgN405bESKGc+y1HLpuUrweIsyKUR/uM07AGdVzuBwy7 lU8/2Vg3GKZpnKbDTrwyesmJDQnd59afW43F9GEs= From: ZyX To: Bart Schaefer , "zsh-users@zsh.org" In-Reply-To: <150222172204.ZM19090@torch.brasslantern.com> References: <20150222132310.GA18377@wintermute> <150222111007.ZM18687@torch.brasslantern.com> <4497961424642126@web27g.yandex.ru> <150222172204.ZM19090@torch.brasslantern.com> Subject: Re: ANSI bg colour outside of prompt area MIME-Version: 1.0 Message-Id: <4975571424694843@web14h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Mon, 23 Feb 2015 15:34:03 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r 23.02.2015, 04:23, "Bart Schaefer" : > 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.