unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: nospam@spamgourmet.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Update filename history after several actions
Date: Sat, 08 Oct 2005 03:04:34 +0300	[thread overview]
Message-ID: <8764s8vljt.fsf@jurta.org> (raw)
In-Reply-To: <20051004071357.GB30424@www.trapp.net> (Tomas Zerolo's message of "Tue, 4 Oct 2005 09:13:57 +0200")

>> find-file-noselect has an argument NOWARN that probably ought to
>> be--but isn't actually--provided as t by Lisp programs that visit
>> files for their own reasons [...]
>
> Sorry for the random and semi-offtopic nitpick -- but wouldn't be NOUSER
> or NONINTERACTIVE or something along these lines be a less misleading
> name? NOWARN suggests a (related but) different purpose to me.

What about adding a new option with a list of command names compared
in `find-file-noselect' with `this-command' before adding a file name
to the history?  Every package (e.g. dired.el, recentf.el) could add
their own user-level command names to such a variable.

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2005-10-08  0:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87fys87vbv.fsf@ID-24456.user.uni-berlin.de>
     [not found] ` <E1EFXvj-00051R-HS@fencepost.gnu.org>
     [not found]   ` <87r7br1rp9.fsf@ID-24456.user.uni-berlin.de>
     [not found]     ` <E1EFtKY-0004Vy-2X@fencepost.gnu.org>
     [not found]       ` <u8xxtqtpw.fsf@ID-24456.user.uni-berlin.de>
2005-10-04  5:02         ` Update filename history after several actions Richard M. Stallman
2005-10-04  7:13           ` Tomas Zerolo
2005-10-08  0:04             ` Juri Linkov [this message]
2005-10-09 18:16               ` Richard M. Stallman
2005-10-10  6:14                 ` Juri Linkov
2005-10-11 14:46                   ` Richard M. Stallman
2005-10-12  5:47                     ` Juri Linkov
2005-10-13  4:51                       ` Richard M. Stallman
2005-10-13 14:10                         ` Stefan Monnier

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=8764s8vljt.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=nospam@spamgourmet.com \
    --cc=rms@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).