From: Marcin Borkowski <mbork@mbork.pl>
To: Alexander Klimov <alserkli@inbox.ru>
Cc: emacs-devel@gnu.org
Subject: Re: insert-file-name-into-minibuffer
Date: Sat, 09 Feb 2019 22:38:53 +0100 [thread overview]
Message-ID: <87bm3ky74i.fsf@mbork.pl> (raw)
In-Reply-To: <b28d826f6c728c61549140257bbb0354@a4b8821e521f95dc12328aa66fab76992>
On 2019-02-09, at 22:30, Alexander Klimov <alserkli@inbox.ru> wrote:
> On Sat, 9 Feb 2019, Eli Zaretskii wrote:
>> > It is quite common to insert the name of the current file into the
>> > argument of shell-command or compile command (both use
>> > read-shell-command). I wonder what it the preferred way to do it?
>>
>> Doesn't M-n in the minibuffer already do that?
>
> Thanks, never knew it works in read-shell-command this way!
>
> OTOH, next-history-element replaces the whole line even if one
> already typed `gcc ...' and does not allow to insert the file name
> with full path.
>
> Speaking of buffer file names, probably there should also be a more
> direct way to copy the full path of the current file than C-x C-f M-n
> C-S-backspace.
Not entirely what you're looking for, but are you aware of `w', `C-u w'
and `C-u 0 w' in Dired?
Hth,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2019-02-09 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 14:39 insert-file-name-into-minibuffer Alexander Klimov
2019-02-09 14:50 ` insert-file-name-into-minibuffer Eli Zaretskii
2019-02-09 21:30 ` insert-file-name-into-minibuffer Alexander Klimov
2019-02-09 21:38 ` Marcin Borkowski [this message]
2019-02-09 21:50 ` insert-file-name-into-minibuffer Alexander Klimov
2019-02-09 21:59 ` insert-file-name-into-minibuffer Marcin Borkowski
2019-02-09 22:19 ` insert-file-name-into-minibuffer Alexander Klimov
2019-02-13 18:49 ` insert-file-name-into-minibuffer Marcin Borkowski
2019-02-17 7:09 ` insert-file-name-into-minibuffer Marcin Borkowski
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=87bm3ky74i.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=alserkli@inbox.ru \
--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).