unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stuart D. Herring" <herring@lanl.gov>
Cc: emacs-devel@gnu.org
Subject: Re: Recent documents: Emacs and GNOME integration
Date: Tue, 30 May 2006 14:10:40 -0700 (PDT)	[thread overview]
Message-ID: <37157.128.165.123.132.1149023440.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <20060530195948.37508.qmail@web51014.mail.yahoo.com>

> I was going to respond that the ~/.recently-used file has to be visited
> in order to make the necessary changes, and that it's only important
> that the buffer's state matches the file in the case that the user had
> previously visited the file himself/herself.  But your question made me
> realize that the file's contents could be updated in a temporary buffer
> and then written to disk -- except that the question of what to do in
> case the file is already visited in a buffer becomes even trickier,
> especially if the buffer has been modified.

Just see if the file is already being visited (`get-file-buffer') and use
its visiting buffer (complete with the "written" message) if so.  The only
problem then is if the user has made that buffer incompatibly formatted. 
But then again, this could already happen with the file, so it's not an
additional difficulty.

I might also point out that the other things `write-region' does without
the message-suppressing VISIT argument can be done with
`set-visited-file-name' and `set-visited-file-modtime'.  Maybe that helps
when doing it the way you want?

Davis

PS - You may realize it perfectly well, but in case you don't: you haven't
been including emacs-devel in your posts as far as I can tell.

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.

  parent reply	other threads:[~2006-05-30 21:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1147396844.567992.55920@i40g2000cwc.googlegroups.com>
2006-05-13  4:51 ` Recent documents: Emacs and GNOME integration Richard Stallman
2006-05-17  7:50   ` Mathias Dahl
2006-05-17 14:37     ` Piotr Zielinski
2006-05-17 18:50       ` Stuart D. Herring
2006-05-17 19:01         ` Stuart D. Herring
2006-05-17 23:12       ` Richard Stallman
2006-05-24 18:52         ` Kevin Rodgers
2006-05-25  0:37           ` Richard Stallman
2006-05-25 17:22             ` Bill Wohler
2006-05-26 18:54               ` Kevin Rodgers
2006-05-30 15:46                 ` Stuart D. Herring
     [not found]                   ` <20060530163850.34480.qmail@web51010.mail.yahoo.com>
2006-05-30 18:28                     ` Stuart D. Herring
     [not found]                       ` <20060530195948.37508.qmail@web51014.mail.yahoo.com>
2006-05-30 21:10                         ` Stuart D. Herring [this message]
2006-05-25 17:02           ` Stuart D. Herring
2006-05-17 20:08     ` Richard Stallman

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=37157.128.165.123.132.1149023440.squirrel@webmail.lanl.gov \
    --to=herring@lanl.gov \
    --cc=emacs-devel@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 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).