unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: move-beginning-of-line
Date: Tue, 15 Mar 2005 13:39:05 -0500	[thread overview]
Message-ID: <E1DBGwb-0002PA-7f@fencepost.gnu.org> (raw)
In-Reply-To: <m3fyyywsd6.fsf@kfs-l.imdomain.dk> (storm@cua.dk)

    > Sorry for replying so late to this, but is there some extremely good
    > (that is, absolutely unavoidable) reason why that image is layed on
    > top of text that _ends in a newline_ (or just contains newlines)?

The general idea of of auto-image-file-mode, and of my new replacement
image-mode, is that the image sits on top of the text of the file.
This is so if you write the buffer to some other file, it will get the
right contents.  As long as we keep that idea, there will be newlines
in the file.

However, insert-image-file doesn't necessarily have to work this way.
It could instead make the image sit on top of a space, like
insert-image.

Does anyone see a reason why not to do this?

  parent reply	other threads:[~2005-03-15 18:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 23:01 move-beginning-of-line Kim F. Storm
2005-03-14  2:58 ` move-beginning-of-line Luc Teirlinck
2005-03-14  8:20   ` move-beginning-of-line Kim F. Storm
2005-03-14 16:48     ` move-beginning-of-line Ralf Angeli
2005-03-14 17:31       ` move-beginning-of-line David Kastrup
2005-03-14 17:52         ` move-beginning-of-line Ralf Angeli
2005-03-14 18:48       ` move-beginning-of-line Stefan Monnier
2005-03-15 18:38         ` move-beginning-of-line Richard Stallman
2005-03-15 18:39     ` Richard Stallman [this message]
2005-03-15 22:23     ` move-beginning-of-line David Kastrup
     [not found] ` <m364zqibx2.fsf@zsu.sush.org>
2005-03-17 15:34   ` move-beginning-of-line Kim F. Storm

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=E1DBGwb-0002PA-7f@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=teirllm@dms.auburn.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).