unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 37573@debbugs.gnu.org, tim.zander@kit.edu
Subject: bug#37573: 27.0.50; Remote file opened from GNOME-Nautilus
Date: Tue, 08 Oct 2019 16:11:35 +0300	[thread overview]
Message-ID: <838spvxtyw.fsf@gnu.org> (raw)
In-Reply-To: <871rvnpf71.fsf@gmx.de> (message from Michael Albinus on Tue, 08 Oct 2019 14:57:54 +0200)

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: tim.zander@kit.edu,  37573@debbugs.gnu.org
> Date: Tue, 08 Oct 2019 14:57:54 +0200
> 
> +*** Gnome: Navigation from Nautilus to remote files.
> +
> +If you navigate to a file in Nautilus via "Open With Emacs", which
> +belongs to a remote server, you might not be able to save this file

I suggest to reorder the words in the beginning of this sentence:

  If you navigate to a file, which belongs to a remote server, in
  Nautilus via "Open With Emacs" you might not be able to save this
  file[...]

Does this describe the situation correctly?

The original wording made it hard to understand what "belongs to a
remote server".

> +once you have modified it in Emacs. The reasons for failing are
                                     ^^
Two spaces.

> +different, and for some connection methods it might even be possible.

Here' I'd rephrase

  The reasons for the failure can vary, and for some connection
  methods saving the file might even succeed.

> +A better approach might be to avoid navigation from Nautilus to Emacs
> +for such files, and to open the file in Emacs using Tramp remote file
                   ^^^^^^^^^^^^^^^^^^^^
"and instead to open the file..."

Thanks.





  reply	other threads:[~2019-10-08 13:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 15:00 bug#37573: 27.0.50; Remote file opened from GNOME-Nautilus Tim Zander
2019-10-06 10:37 ` Michael Albinus
2019-10-06 17:44   ` Eli Zaretskii
2019-10-07  7:55     ` Michael Albinus
2019-10-07 16:28       ` Eli Zaretskii
2019-10-08 12:57         ` Michael Albinus
2019-10-08 13:11           ` Eli Zaretskii [this message]
2019-10-08 13:44             ` Michael Albinus
2019-10-08 14:15               ` Tim Zander

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=838spvxtyw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37573@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=tim.zander@kit.edu \
    /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).