From: Miles Bader <miles@gnu.org>
To: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Visual line movement inconsistency
Date: Sat, 30 Aug 2008 08:53:39 +0900 [thread overview]
Message-ID: <87tzd3idj0.fsf@catnip.gol.com> (raw)
In-Reply-To: <87prnrheq1.fsf@kfs-lx.rd.rdm> (Kim F. Storm's message of "Fri, 29 Aug 2008 20:13:10 +0200")
storm@cua.dk (Kim F. Storm) writes:
>> So far it all seems pretty reasonable to me.
>
> IMO, there should be at least an option to show "word wrap" indicators
> in the fringes. You may disagree...
>
> In any case, if you create a very long word which spans more than one line in
> word wrap mode, the "wrap" indicates are not shown to indicate that the
> line does indeed continue. That's a bug that I reported some time ago.
I think it might be useful to have distinct indicators for the two types
of wrapping, yes. If there was such a feature, visual-line-mode (please
distinguish this from "word wrap mode", as they're not the same thing)
could use it to show indicators for non-word wrapping while suppressing
those for normal word-wrapping. That would probably make most users
happy.
However that's mainly useful for the "very long word" wrapping case you
mention, and that's a pretty rare occurance, so it doesn't seem like a
particularly critical thing. If someone decides to put in the time to
implement it, great; otherwise, whatever.
-Miles
--
Quotation, n. The act of repeating erroneously the words of another. The words
erroneously repeated.
next prev parent reply other threads:[~2008-08-29 23:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 13:45 Visual line movement inconsistency Tassilo Horn
2008-08-29 0:46 ` Miles Bader
2008-08-29 7:18 ` Tassilo Horn
2008-08-29 7:54 ` Lennart Borgman (gmail)
2008-08-29 12:02 ` Kim F. Storm
2008-08-29 14:59 ` Miles Bader
2008-08-29 18:13 ` Kim F. Storm
2008-08-29 23:53 ` Miles Bader [this message]
2008-08-30 15:35 ` Kim F. Storm
2008-08-30 23:53 ` Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tzd3idj0.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.