unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 4318@debbugs.gnu.org, gottlieb@nyu.edu
Subject: bug#4318: 23.1; trouble indenting looooong lines with visual-line-mode
Date: Sun, 18 Sep 2011 09:56:40 +0200	[thread overview]
Message-ID: <m3ty8a1dxj.fsf@stories.gnus.org> (raw)
In-Reply-To: <83ty8btshc.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Sep 2011 12:42:39 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> The extra line stands for the space that is not shown.  If you place
> the cursor on that "empty line" and type "C-x =", you will see that
> point is before the space character, not before newline.
>
> So I think visual-line-mode (a.k.a. "word wrap") behaves correctly.
> Doing what the OP asks for would also have undesirable side effects,
> albeit different ones.  E.g., adding some non-white character at the
> beginning of that line will suddenly and mysteriously move the
> "xxxx..." part one line down.

I think that's probably desired.

The point of `visual-line-mode' is to (visually) do word wrap between
words to keep lines short(ish).  Folding before there even has been a
word looks odd to me.

On the other hand, it does make the lines visually shorter, so it's
debatable...

> And that's even before I consider the potential complications of the
> code, which already tracks the word wrap mode with no less than 12
> state variables...

:-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  reply	other threads:[~2011-09-18  7:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 14:13 bug#4318: 23.1; trouble indenting looooong lines with visual-line-mode Allan Gottlieb
2011-09-17  7:23 ` Lars Magne Ingebrigtsen
2011-09-17  9:42   ` Eli Zaretskii
2011-09-18  7:56     ` Lars Magne Ingebrigtsen [this message]
2011-09-18 15:26     ` Chong Yidong
2015-12-15 10:51 ` bug#4318: GMNT p8

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=m3ty8a1dxj.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=4318@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gottlieb@nyu.edu \
    /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).