unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Chong Yidong <cyd@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history of visited files
Date: Sun, 13 Jan 2013 10:21:25 +0100	[thread overview]
Message-ID: <50F27C95.6050804@easy-emacs.de> (raw)
In-Reply-To: <87obgug641.fsf@gnu.org>

Am 12.01.2013 09:25, schrieb Chong Yidong:
> Dani Moncayo <dmoncayo@gmail.com> writes:
>
>>> The history of visited files should contain every visited
>>> file, regardless of the way it was visited (command line argument,
>>> drag-n-drop, menu item, C-x C-f...)
>>
>> ... and when the file is visited via bookmarks (e.g. `C-x r b foo
>> <RET>').  (I've just missed this feature).
>
> This feature is relatively easy to implement.
>
> I think it is best done by adding an optional argument `add-history' to
> `find-file' (and similar functions like `find-file-other-frame'), so
> that Lisp callers can specify to update `file-name-history' even if the
> file name was not read interactively.  Any objections?
>
>
>
>

Hi,

don't think files just used by programs should go into history. That might make history useless to a certain point.
Also it might slow down programs.

Cheers,

Andreas



       reply	other threads:[~2013-01-13  9:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAH8Pv0gLmqr45OQ4N8zxBGWv9ztmyG2dkbERjkFGA-Z=hc7AeA@mail.gmail.com>
     [not found] ` <ep3908calm.fsf@fencepost.gnu.org>
     [not found]   ` <CAH8Pv0iKxAp_3kLz=KVfV=mcb1jUOq_TfV7oHNhSNL5LXh8FqQ@mail.gmail.com>
     [not found]     ` <CAH8Pv0gpDneCVBsitrzMa-tVFDiXvXQUCBo-upzQQBfjcFgREw@mail.gmail.com>
     [not found]       ` <87obgug641.fsf@gnu.org>
2013-01-13  9:21         ` Andreas Röhler [this message]
2013-01-13 16:28           ` bug#12915: 24.2.50; Visiting a file via drag-and-drop should add it to the history of visited files 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

  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=50F27C95.6050804@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=cyd@gnu.org \
    --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).