bug#16837: 24.3.50; Allow a HISTORY arg for `read-file-name', `read-file-name-default'

bug#16837: 24.3.50; Allow a HISTORY arg for `read-file-name', `read-file-name-default'

[Drew Adams]

An enhancement request -

Please consider allowing an optional HISTORY arg to these functions
(with the default value being of course `file-name-history').

It can happen that someone wants the behavior of one of these functions,
but with a different file-name history, such as `shell-command-history'.


In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2014-02-11 on ODIEONE
Bzr revision: 116410 lekktu@gmail.com-20140211204823-l9l2s6tktfitq266
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
 CPPFLAGS=-Ic:/Devel/emacs/include'

bug#16837: 24.3.50; Allow a HISTORY arg for `read-file-name', `read-file-name-default'

[Lars Ingebrigtsen]

Drew Adams <drew.adams@oracle.com> writes:

> Please consider allowing an optional HISTORY arg to these functions
> (with the default value being of course `file-name-history').
>
> It can happen that someone wants the behavior of one of these functions,
> but with a different file-name history, such as `shell-command-history'.

Yes, that seems potentially useful.  It currently uses the hard-coded
`file-name-history' history.

Anybody have any objections to adding this?  I see one possible
complication -- it'll be Yet Another Optional Parameter that has to be
passed on to `read-file-name-function', and if somebody has defined that
to take fewer parameters, it'll bomb...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#16837: 24.3.50; Allow a HISTORY arg for `read-file-name', `read-file-name-default'

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Yes, that seems potentially useful.  It currently uses the hard-coded
> `file-name-history' history.
>
> Anybody have any objections to adding this?  I see one possible
> complication -- it'll be Yet Another Optional Parameter that has to be
> passed on to `read-file-name-function', and if somebody has defined that
> to take fewer parameters, it'll bomb...

And thinking about this for five more years, I think that's a pretty
serious objection -- the argument list is part of the API here, so we
can't really just add another parameter here.

So people that want a different history variable here will have to make
their own `read-file-name-function' function.

Closing.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no