From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Documentation fix
Date: Sat, 08 Apr 2023 18:37:52 +0300 [thread overview]
Message-ID: <83lej2mlkf.fsf@gnu.org> (raw)
In-Reply-To: <87wn2nolt1.fsf@yahoo.com> (message from Po Lu on Fri, 07 Apr 2023 21:37:30 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Fri, 07 Apr 2023 21:37:30 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Does this mean the function gets on the basename of the file, without
> > any leading directories? Or does it mean something else?
>
> Yes.
>
> >> + The function should return the complete file name under which the
> >> +file should be saved, including the directory where it should be
> >> +saved, under which Emacs will ask the other program to save the file.
> >
> > How would the function know what is the "right" directory to save the
> > file? Without some hints to that effect, this documentation is not
> > very useful, IMO.
>
> How about:
>
> For example, a function defined for Dired buffers may want to return
> the directory containing the file under the position of the drop.
>
> >> + If the file was successfully saved,
> >
> > And if not?
>
> Emacs never gets a reply from the program performing the drop, and thus
> cannot do anything.
>
> >> the function is called again,
> >> +this time with the first argument set to @code{nil}, and the second
> >> +argument set to the file name that was returned. The function should
> >> +then perform whatever action is appropriate (i.e., opening the file or
> >> +refreshing a directory listing.) ^^^^
> >
> > I guess, you mean "e.g." there.
>
> Yes, sorry.
>
> > More importantly, I don't understand why would Emacs need to do
> > anything with the file at all. As a matter of fact, I don't think I
> > understand the purpose of this protocol at all, and I don't see it
> > clarified in the manual. Can you explain what is this used for?
> > Without such explanation, this documentation lacks context without
> > which the information makes no sense.
>
> It allows a program to drop files into a file manager, such as Dired,
> and directly save the file into the directory that is currently open in
> the file manager's window.
>
> This is a three-step process:
>
> 1. The program performing the drop sends the name of a file to Emacs,
> such as gen_sqrtab.c.
>
> 2. Emacs replies with the file name under which the file should be
> saved. If it's dropped on top of a Dired buffer visiting
> /export/home/user/Documents, for example, Emacs should reply with
> /export/home/user/Documents/gen_sqrtab.c.
>
> 3. If saving the file is successful, the program performing the drop
> notifies Emacs, at which point the Dired buffer is reverted.
>
> This protocol is mainly supported by web browsers and GTK based file
> managers, and now Emacs as well.
Thanks. I rewrote the documentation of the XDS support, please take a
look and tell if I made any mistakes.
next prev parent reply other threads:[~2023-04-08 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871qkvq4o4.fsf.ref@yahoo.com>
2023-04-07 12:04 ` Documentation fix Po Lu
2023-04-07 12:18 ` Eli Zaretskii
2023-04-07 13:37 ` Po Lu
2023-04-08 15:37 ` Eli Zaretskii [this message]
2023-04-09 0:37 ` Po Lu
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=83lej2mlkf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
/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).