From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Custom question: different default values for different environments?
Date: Wed, 30 Apr 2003 10:19:41 +0200 [thread overview]
Message-ID: <84sms0s8gy.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <E19AkNc-0008FZ-00@fencepost.gnu.org> (Richard Stallman's message of "Wed, 30 Apr 2003 01:43:44 -0400")
Richard Stallman <rms@gnu.org> writes:
> After some discussion among the Tramp developers, it turns out that
> it is probably best to just have two entries everywhere: one entry
> mentioning rsh and another entry mentioning remsh.
>
> Sorry, I do not understand what you are proposing. Would you please
> explain more clearly?
Originally, I asked how to achieve a certain effect in defcustom.
Now the plan is to do something entirely different, and a side effect
of that plan is that the effect I originally asked about isn't needed
anymore.
The old plan was to allow the user to type filenames
"/rsh:user@host:bla" and the system would know whether to invoke rsh
or remsh.
The new plan is to require the user to type "/rsh:user@host:bla" if
rsh is to be invoked, and "/remsh:user@host:bla" if remsh is to be
invoked.
With the new plan, the file name corresponds to the Unix command being
used, and I guess that people are familiar with those names.
(Ideally, autodetection of the command to be used to contact the
remote host would be desirable. But it takes a long time to try
several methods for connecting. So users have to specify the command
in the file name.)
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
next prev parent reply other threads:[~2003-04-30 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 13:05 Custom question: different default values for different environments? Kai Großjohann
2003-04-28 23:38 ` Richard Stallman
2003-04-29 15:40 ` Kai Großjohann
2003-04-30 5:43 ` Richard Stallman
2003-04-30 8:19 ` Kai Großjohann [this message]
2003-05-01 3:20 ` Richard Stallman
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=84sms0s8gy.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).