From: Eli Zaretskii <eliz@gnu.org>
To: Luis Gerhorst <privat@luisgerhorst.de>
Cc: 35434@debbugs.gnu.org
Subject: bug#35434: [<8; 36; 7m26.2; terminal emacs: continuation line indicator missing when word wrapping is enabled
Date: Fri, 26 Apr 2019 14:10:04 +0300 [thread overview]
Message-ID: <831s1pxbsj.fsf@gnu.org> (raw)
In-Reply-To: <m2lfzxtcip.fsf@luis-imac.fritz.box> (message from Luis Gerhorst on Fri, 26 Apr 2019 10:07:58 +0200)
> From: Luis Gerhorst <privat@luisgerhorst.de>
> Date: Fri, 26 Apr 2019 10:07:58 +0200
>
> 1. Start Emacs using 'emacs -Q --no-window-system'.
>
> 2. Reduce the window width until the lines in the scratch buffer wrap
> around. Notice that Emacs shows a '\' at the end of each wrapped line.
>
> 3. Type M-x toggle-word-wrap. Emacs no longer shows a '\' to indicate
> continuation lines. There is no way to tell whether the line contains a
> newline, or whether it has been wrapped.
>
> Notice that if you do the same in graphical Emacs (i.e. start with
> 'emacs -Q'), the fringes do show an indicator for continuation lines,
> even with word wrapping enabled.
The canonical way of using this feature is with "M-x visual-line-mode",
not with toggle-word-wrap. visual-line-mode takes care of removing
the fringe indicators as well, so the appearance on GUI frames and TTY
frames is the same: without continuation indicators.
toggle-word-wrap does part of the job of visual-line-mode, and frankly
I don't understand why the former even exists.
Making continuation glyphs appear in TTY frames shouldn't be hard, but
I don't know how important is that.
next prev parent reply other threads:[~2019-04-26 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 8:07 bug#35434: [<8; 36; 7m26.2; terminal emacs: continuation line indicator missing when word wrapping is enabled Luis Gerhorst
2019-04-26 8:12 ` bug#35434: " Luis Gerhorst
2019-04-26 11:10 ` Eli Zaretskii [this message]
2019-04-26 11:29 ` Luis Gerhorst
2019-04-26 11:33 ` Eli Zaretskii
2019-04-26 11:49 ` Luis Gerhorst
2019-04-26 12:10 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831s1pxbsj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35434@debbugs.gnu.org \
--cc=privat@luisgerhorst.de \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).