unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: emacs-devel@gnu.org
Subject: Re: [GNU ELPA] New package: tramp-locproc
Date: Thu, 02 Jan 2025 12:47:38 +0100	[thread overview]
Message-ID: <87cyh5309x.fsf@gmx.de> (raw)
In-Reply-To: <87frm2uv02.fsf@> ("Björn Bidar"'s message of "Wed, 01 Jan 2025 22:41:49 +0200")

Björn Bidar <bjorn.bidar@thaodan.de> writes:

Hi Björn,

>> I would like to submit a new package to GNU ELPA: tramp-locproc.
>>
>
> Why not make this a opt-in tramp-module? I wonder if a longer name would
> be better as it does speak better for it self. Why not tramp-local-process?

I don't want to add it to Tramp proper, because it implements something
out of the canonical remote files spec. Moreover, for the "sshfs"
method, it overwrites the default implementation. This might confuse
people.

And I don't know whether it is mature enough to be used. First, I'd like
to get user feedback.

About the package name ... I thought indeed to use the longer one, as
you've proposed. Finally, I've decided for the shorter one. I don't see
a disadvantage, people decide to use a package based on the description,
not on the name.

>> Beside the obvious advantage to run local processes over remote files,
>> there is also the disadvantage that file names are adapted in order to
>> reflect their local mount location.
>
> When displayed in Emacs or for the processes executed?

Both.

>>     ;; Replace handler functions.
>>     (setcdr (assq 'exec-path val) #'tramp-locproc-handle-exec-path)
>>     (setcdr (assq 'make-process val) #'tramp-locproc-handle-make-process)
>>     (setcdr (assq 'process-file val) #'tramp-locproc-handle-process-file)
>>     (setcdr (assq 'shell-command val) #'tramp-locproc-handle-shell-command)
>>     (setcdr (assq 'start-file-process val) #'tramp-handle-start-file-process)))
>
> You it be possible to make this a default or fallback action depending
> on the users intention? E.g. by using a prefix arg to invert the
> default.
>
> The default then being either to call the command as a local process by
> default or explicitly by using a prefix argument.

Might be an extension for later. But I fear people get confused. The
don't call `make-process' directly, the call something like `compile' or
`grep-find', which have their own idea of prefix arguments.

So we'll need rather an explict enable/disable knob. Added to the TODO.

Best regards, Michael.



      parent reply	other threads:[~2025-01-02 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30 16:22 [GNU ELPA] New package: tramp-locproc Michael Albinus
2025-01-01 20:41 ` Björn Bidar
     [not found] ` <87frm2uv02.fsf@>
2025-01-02 11:47   ` Michael Albinus [this message]

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=87cyh5309x.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=bjorn.bidar@thaodan.de \
    --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).