From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9296@debbugs.gnu.org
Subject: bug#9296: 24.0.50; next-line/prev-line on lines with images
Date: Sun, 14 Aug 2011 21:37:41 +0200 [thread overview]
Message-ID: <m3obzr2396.fsf@stories.gnus.org> (raw)
In-Reply-To: <83vctzvldp.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 14 Aug 2011 22:33:22 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> I haven't seen this behaviour before, I think, and it's odd that I
>> haven't noticed, since I'm using images heavily in several modes...
>
> Which behavior are you talking about? The one that still exists with
> the current trunk, or the one I fixed today?
The behaviour after the last fix. It's not the same as the
(non-perfect) Emacs 23 behaviour on long `truncate-line' lines.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-08-14 19:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 20:56 bug#9296: 24.0.50; next-line/prev-line on lines with images Lars Ingebrigtsen
2011-08-14 7:17 ` Eli Zaretskii
2011-08-14 11:13 ` Eli Zaretskii
2011-08-14 14:16 ` Lars Magne Ingebrigtsen
2011-08-14 14:19 ` Lars Magne Ingebrigtsen
2011-08-14 16:52 ` Eli Zaretskii
2011-08-14 17:00 ` Lars Magne Ingebrigtsen
2011-08-14 19:33 ` Eli Zaretskii
2011-08-14 19:37 ` Lars Magne Ingebrigtsen [this message]
2011-08-14 20:02 ` Eli Zaretskii
2011-08-14 20:23 ` Lars Magne Ingebrigtsen
2011-08-14 20:50 ` Eli Zaretskii
2011-08-14 21:12 ` Lars Magne Ingebrigtsen
2011-08-15 6:47 ` Eli Zaretskii
[not found] ` <m362lyvrt6.fsf@stories.gnus.org>
[not found] ` <83aabavq9k.fsf@gnu.org>
2011-08-15 12:06 ` Lars Magne Ingebrigtsen
2011-08-14 17:10 ` Lars Magne Ingebrigtsen
2011-08-14 19:39 ` Eli Zaretskii
2011-08-14 21:43 ` Johan Bockgård
2011-08-15 6:48 ` Eli Zaretskii
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=m3obzr2396.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=9296@debbugs.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.
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.