From: Emanuel Berg <moasenwood@zoho.eu>
To: ding@gnus.org
Subject: another Emacs 25 (?) issue with attachments: cannot change file name
Date: Sun, 05 May 2019 01:49:34 +0200 [thread overview]
Message-ID: <861s1du6ep.fsf@zoho.eu> (raw)
I've now experienced another attachments issue
since upgrading to Emacs 25 [1]. It seems
I cannot change the file name as I download
(move) it (the attachment) to the prefered
destination on my drive - I can only pick
the location!
After typing the path, hitting RET will have
the file end up there, yes, but typing the path
_and a new filename_ will say [No match]
instead of, as before, rename the file
as entered as well.
To not do this anymore, I do
`gnus-summary-save-parts', then just hit RET
until it asks for the location, which I type
and then hit RET.
[1] GNU Emacs 25.1.1
(arm-unknown-linux-gnueabihf, GTK+ Version
3.22.11) of 2017-09-16, modified by Debian
Gnus v5.13
--
underground experts united
http://user.it.uu.se/~embe8573
next reply other threads:[~2019-05-04 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 23:49 Emanuel Berg [this message]
2019-05-05 11:46 ` Eric S Fraga
2019-05-05 22:10 ` Emanuel Berg
2019-05-20 15:33 ` Emanuel Berg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=861s1du6ep.fsf@zoho.eu \
--to=moasenwood@zoho.eu \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).