From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id e9cf25d9 for ; Mon, 30 Dec 2019 16:08:53 +0000 (UTC) Received: (qmail 14875 invoked by alias); 30 Dec 2019 16:08:42 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 45158 Received: (qmail 22952 invoked by uid 1010); 30 Dec 2019 16:08:42 -0000 X-Qmail-Scanner-Diagnostics: from mail-lf1-f41.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25677. spamassassin: 3.4.2. Clear:RC:0(209.85.167.41):SA:0(-1.9/5.0):. Processed in 1.949058 secs); 30 Dec 2019 16:08:42 -0000 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.167.41 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oMlTppXfSY/0WzPYNRlFgQiwXsTA4LIcC/JkVnjvi9s=; b=pEithm3ybS5J0oGqS2iYxQdjByNlkF7+REL7T6hXqOgVwJgeqJTXcDBNIUZ5cHsApv z0QIuj8OFk+tLSeh+oyKdhJZVUipC0471pPm6aEGVgq1XY3jG1oHMVEk+POKPTTxol3x agRNJJTIPkGiu1xBrJQcxlQyTN+ks60CtnoaC7T3sKnIcWs2YXkXY6GB52wFDlzt20Nz CD0FdovClnJX0Mv4jLdh8rVUIryTaSW7xkDmsl0YPZBx3ihTNIv/GjLRTrVtGmp2Hqn5 OBGKJiHV9DcibVKqS7h2rg7W0JhhBYtS11d4Mz4IkcnkQlmoYxLlsy80/PLKyRuJiCht HMJQ== X-Gm-Message-State: APjAAAUimot0ChEzSjzyXi1fdmiISfN2fVSC2zrA6l+A+C2C5V8Cc+Ji LDBX5okyOTcanTuWr+vy1/SlnEv6kWVcAVrk8ulo6Q== X-Google-Smtp-Source: APXvYqwAIB4FI5wHfVKfGrrOolsZyp0N1xLTugS5nMZBnW2k90QhwwsUjaiKqG0Jp7OzGYw4IxIdQeyjga6nuQwEVsY= X-Received: by 2002:ac2:48bc:: with SMTP id u28mr38043832lfg.81.1577722085045; Mon, 30 Dec 2019 08:08:05 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Bart Schaefer Date: Mon, 30 Dec 2019 08:07:53 -0800 Message-ID: Subject: Re: Feature request: italic style in region_highlight To: Roman Perepelitsa Cc: Sebastian Gniazdowski , Zsh hackers list Content-Type: text/plain; charset="UTF-8" On Mon, Dec 30, 2019 at 2:17 AM Roman Perepelitsa 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).