unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Luis Gerhorst <privat@luisgerhorst.de>
Cc: 35434@debbugs.gnu.org
Subject: bug#35434: terminal emacs: continuation line indicator missing when word wrapping is enabled
Date: Fri, 26 Apr 2019 15:10:04 +0300	[thread overview]
Message-ID: <83v9z1vug3.fsf@gnu.org> (raw)
In-Reply-To: <m27ebh2dhn.fsf@luisgerhorst.de> (message from Luis Gerhorst on Fri, 26 Apr 2019 13:49:08 +0200)

> From: Luis Gerhorst <privat@luisgerhorst.de>
> Cc: 35434@debbugs.gnu.org
> Date: Fri, 26 Apr 2019 13:49:08 +0200
> 
> > Would you perhaps like to describe the idea behind the patch you
> > would like to submit before actually coding it?  This could avoid
> > the need to rework it more than necessary.
> 
> Code-wise I have no idea yet ;)
> 
> My initial approach would be to have a look at the patches that
> introduced word wrapping in the first place. If I'm lucky they
> modified the GUI code to still show the fringe indicators, but
> simply missed the TUI code.
> 
> However, I've not read any Emacs C code ever. I'll look into it and
> come back when I unserstand the problem.

Look at the function produce_special_glyphs in xdisp.c.

I think showing the continuation glyphs on TTY frames in word-wrap
mode should be optional, controlled by a user variable, since the
current behavior is unchanged since Emacs 23.

Thanks.





      reply	other threads:[~2019-04-26 12: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 ` bug#35434: [<8; 36; 7m26.2; " Eli Zaretskii
2019-04-26 11:29   ` bug#35434: " Luis Gerhorst
2019-04-26 11:33     ` Eli Zaretskii
2019-04-26 11:49       ` Luis Gerhorst
2019-04-26 12:10         ` Eli Zaretskii [this message]

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=83v9z1vug3.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).