unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Andreas Schwab <schwab@suse.de>
Cc: 37883@debbugs.gnu.org
Subject: bug#37883: 27.0.50; read-file-name: Scrambled INITIAL
Date: Wed, 23 Oct 2019 14:40:38 +0200	[thread overview]
Message-ID: <87ftjjmy7t.fsf@web.de> (raw)
In-Reply-To: <mvm36fjsstt.fsf@suse.de> (Andreas Schwab's message of "Wed, 23 Oct 2019 11:40:30 +0200")

Andreas Schwab <schwab@suse.de> writes:

> > in emacs -Q (with default-directory -> ~/)
> >
> >   (read-file-name-default "File: " nil nil nil "~/.bash_history" nil)
> >
> > prompts with default minibuffer contents "/:~/~/.bash_history".  No part
> > of that is shadowed (to indicate which part is meaningful).  Without
> > fully understanding how the initial contents are calculated, it doesn't
> > seem very useful with the doubled ~/.  Why can't INITIAL be used
> > literally?
>
> I think INITIAL is supposed to be a file name component, not a full file
> name.  (The manual also discourages the use of INITIAL.)

I have no clue.  The manual describes INITIAL as "initial file name".

I think the INITIAL arg can be casually useful.  In my case I'm setting
the value of a (file name valued) widget with the current value as
INITIAL value which feels quite natural (or, would feel, if it worked as
I expect).


Regards,

Michael.





  reply	other threads:[~2019-10-23 12:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  9:23 bug#37883: 27.0.50; read-file-name: Scrambled INITIAL Michael Heerdegen
2019-10-23  9:40 ` Andreas Schwab
2019-10-23 12:40   ` Michael Heerdegen [this message]
2019-10-23 13:20     ` Michael Albinus
2019-10-23 14:53       ` Michael Heerdegen
2019-10-23 16:24         ` Michael Albinus
2019-10-25  8:45           ` Eli Zaretskii
2022-01-28 16:04             ` Lars Ingebrigtsen
2019-10-23 15:16   ` Michael Heerdegen

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=87ftjjmy7t.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=37883@debbugs.gnu.org \
    --cc=schwab@suse.de \
    /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).