[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#26591: 26.0.50; Using local emacs+tramp with remote emacsclient

From: Peder O. Klingenberg
Subject: bug#26591: 26.0.50; Using local emacs+tramp with remote emacsclient
Date: Sat, 29 Apr 2017 21:45:15 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (darwin)

Eli Zaretskii <address@hidden> writes:

> server-use-tcp is not described in the manual, so I think we should
> add its description somewhere, and then reference that place from this
> text.

I added a new node to the manual, "TCP Emacs server", and
collected/wrote documentation on the various related variables there.
Does this type of doc reorganization require its own NEWS entry?  I
didn't see the point, and so didn't write any.

As this is only tangentially related to the new feature, I made it into
a separate patch.  The updated feature patch applies on top of this
documentation patch, and references the new node.

> "/home" should be in @file, not @samp.  Also, I don't see "/home" used
> anywhere in the example, so something is missing here.

I have hopefully clarified the wording and fixed the tagging and typos.
I noticed while writing the TCP server doc that Emacs was capitalized
elsewhere in the docs, so I updated the capitalization in the paragraphs
on the new option.

Jeez, writing good docs is hard.  Criticisms welcome.  :)

> Why the test for argv[i] being an absolute file name?  And if relative
> file names cannot be supported, I think emacsclient should emit an
> error message rather than silently ignoring --tramp.

As I explained in my previous mail, both absolute and relative filenames
are supported.  There are no code changes in this updated patch set.

Attachment: 0001-Improve-documentation-of-TCP-mode-of-server.el.patch
Description: Text Data

Attachment: 0002-New-option-T-tramp-for-remote-editing-with-emacsclie.patch
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]