unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Help-gnu-emacs@gnu.org
Subject: Re: visual line mode
Date: Sat, 13 Oct 2012 17:26:13 +0200	[thread overview]
Message-ID: <EF1C9AD3-CCD5-4CFB-AC6C-29C1D1F21CE2@Web.DE> (raw)
In-Reply-To: <83d30m7rhg.fsf@gnu.org>


Am 13.10.2012 um 09:36 schrieb Eli Zaretskii:

> As for the cursor not jumping to the end of line: Emacs cannot put the
> cursor where there's no text.

This is as clear as a clear day. Or night. I would have reported a bug when I would have encountered something like that. And I was not complaining that the text cursor jumped from EOL (end of line) in column 47 to column 23 (when the line's so short, how can the text cursor stay far out in space?), what I miss is that it does not jump to column 61 where the other line actually ends but stayed in column 47.

OTOH, what I tried to show with my screen-shot looks exactly like something impossible: the text cursor beyond the end of the line of text. After the word "xdv2pdf" cannot be any white space because it was certainly removed before (I can't remember that replace-regexp was failing before) and because it was not shown in the other wider buffer. Was GNU Emacs a bit confused because the first part of the line it had to break was longer than the window is wide?

--
Greetings

  Pete

We are usually convinced more easily by reasons we have found ourselves than by those which have occurred to others.
				– Blaise Pascal




  reply	other threads:[~2012-10-13 15:26 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12  6:56 visual line mode drain
2012-10-12  8:23 ` Tassilo Horn
2012-10-12  8:24 ` Eli Zaretskii
2012-10-12  8:48   ` Tassilo Horn
2012-10-12 10:35     ` drain
2012-10-12 10:45       ` Peter Dyballa
2012-10-12 10:48         ` drain
2012-10-12 11:27           ` Peter Dyballa
2012-10-12 11:36             ` Tassilo Horn
2012-10-12 13:32               ` Eli Zaretskii
2012-11-28 15:06                 ` Matt McClure
2012-11-28 17:43                   ` Eli Zaretskii
2012-11-29  3:34                     ` Matt McClure
2012-11-29 13:49                   ` Stefan Monnier
2012-12-01  3:28                     ` Matt McClure
2012-10-12 15:51               ` Peter Dyballa
2012-10-12 13:28             ` Eli Zaretskii
2012-10-12 15:46               ` Peter Dyballa
2012-10-12 16:29                 ` Eli Zaretskii
2012-10-12 22:06                   ` Peter Dyballa
2012-10-13  7:41                     ` Eli Zaretskii
2012-10-13 21:54                       ` Peter Dyballa
2012-10-14  1:56                         ` Bob Proulx
2012-10-14  5:44                         ` Eli Zaretskii
2012-10-16 18:38                           ` drain
2012-10-12 15:55               ` Peter Dyballa
2012-10-12 16:30                 ` Eli Zaretskii
2012-10-12 21:40                   ` Peter Dyballa
2012-10-13  7:36                     ` Eli Zaretskii
2012-10-13 15:26                       ` Peter Dyballa [this message]
2012-10-13 15:39                         ` Eli Zaretskii
2012-10-12 11:03       ` Eli Zaretskii
2012-10-12 11:31       ` Tassilo Horn
2012-10-12 11:46         ` drain
2012-10-12 13:30           ` Tassilo Horn
2012-10-12 14:32             ` drain

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=EF1C9AD3-CCD5-4CFB-AC6C-29C1D1F21CE2@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=Help-gnu-emacs@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.
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).