From: Luis Gerhorst <privat@luisgerhorst.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35434@debbugs.gnu.org
Subject: bug#35434: terminal emacs: continuation line indicator missing when word wrapping is enabled
Date: Fri, 26 Apr 2019 13:49:08 +0200 [thread overview]
Message-ID: <m27ebh2dhn.fsf@luisgerhorst.de> (raw)
In-Reply-To: <83wojhvw4g.fsf@gnu.org>
Eli Zaretskii writes:
>> From: Luis Gerhorst <privat@luisgerhorst.de>
>> Cc: 35434@debbugs.gnu.org
>> Date: Fri, 26 Apr 2019 13:29:49 +0200
>>
>> Eli Zaretskii writes:
>>
>> > Making continuation glyphs appear in TTY frames shouldn't be
>> > hard, but
>> > I don't know how important is that.
>>
>> Would you accept a patch if I manage to create one?
>
> I will definitely review it. If it's clean, and if its smaller
> than
> about 15 lines, we can accept it; longer patches will need you
> to
> assign copyright to the FSF.
>
> 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.
next prev parent reply other threads:[~2019-04-26 11:49 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 [this message]
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=m27ebh2dhn.fsf@luisgerhorst.de \
--to=privat@luisgerhorst.de \
--cc=35434@debbugs.gnu.org \
--cc=eliz@gnu.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.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).