From: Eli Zaretskii <eliz@gnu.org>
To: Help-gnu-emacs@gnu.org
Subject: Re: visual line mode
Date: Sat, 13 Oct 2012 17:39:14 +0200 [thread overview]
Message-ID: <83sj9i5ql9.fsf@gnu.org> (raw)
In-Reply-To: <EF1C9AD3-CCD5-4CFB-AC6C-29C1D1F21CE2@Web.DE>
> From: Peter Dyballa <Peter_Dyballa@Web.DE>
> Date: Sat, 13 Oct 2012 17:26:13 +0200
> Cc: Help-gnu-emacs@gnu.org
>
> what I miss is that it does not jump to column 61 where the other line actually ends but stayed in column 47.
Sorry, but this is not helpful. Column 61 and column 47 don't say
anything to me, unless you show a precise recipe, starting with
"emacs -Q", that would explain what you expect Emacs to do.
> 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?
This is either due to a bug or to some customization (most probably
the latter). Again, please give a recipe to reproduce such a
behavior. It should never happen, and has nothing to do with
visual-line-mode.
next prev parent reply other threads:[~2012-10-13 15:39 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
2012-10-13 15:39 ` Eli Zaretskii [this message]
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=83sj9i5ql9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Help-gnu-emacs@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).