From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Uday S Reddy <u.s.reddy@cs.bham.ac.uk>
Cc: emacs-devel@gnu.org
Subject: Re: Lines again
Date: Fri, 04 Jun 2010 13:04:27 -0400 [thread overview]
Message-ID: <jwvbpbqka2t.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <19465.8001.703000.121823@gargle.gargle.HOWL> (Uday S. Reddy's message of "Fri, 4 Jun 2010 16:44:01 +0100")
>> I think "screen lines" and "visual lines" should be the same, yes.
>> "continuation lines" refer specifically to screen lines that are
>> created because of wrapping (i.e. are not displayed on the same
>> visual line as the beginning of the logical line).
> I am thinking differently.
I just explained the way those terms are used, and from what you go on
writing, you don't seem to disagree.
[...]
> So, I am proposing that you get rid of the `line-move-visual' as a
> user option and revert C-n and C-p to act in the logical/visual manner
> in their appropriate modes. You will make a lot of long-time Emacs
> users a lot happier.
Ah, so that's what it's about. Then thanks for your input, but we've
been through that discussion too many times already. Yes, it's
inconsistent, yes, it's a compromise, no not everybody likes it.
Then (setq line-move-visual nil) in your .emacs and live happily
ever after.
WRT to keyboard macros, yes it's a source of problems, but I think the
solution should go further than just tweaking line-move-visual.
Stefan
PS: Interestingly, Emacs-2[12] already did a form of line-move-visual,
just that their code was doing it in a too naive way which only tried to
pay attention to images and invisible text).
prev parent reply other threads:[~2010-06-04 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 0:28 Lines again Uday S Reddy
2010-06-04 13:43 ` Stefan Monnier
2010-06-04 15:44 ` Uday S Reddy
2010-06-04 16:47 ` Eli Zaretskii
2010-06-04 16:49 ` Eli Zaretskii
2010-06-04 18:41 ` Uday S Reddy
2010-06-04 17:04 ` Stefan Monnier [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=jwvbpbqka2t.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=u.s.reddy@cs.bham.ac.uk \
/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).