unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Feature freeze and Tramp?
Date: Sat, 8 May 2004 20:40:29 -0500 (CDT)	[thread overview]
Message-ID: <200405090140.i491eTW28920@raven.dms.auburn.edu> (raw)
In-Reply-To: <87wu3n4380.fsf@emptyhost.emptydomain.de> (message from Kai Grossjohann on Sat, 08 May 2004 12:34:23 +0200)

Kai Grossjohann wrote:
   
   If you (setq tramp-debug-buffer t) then you can see in the *debug
   tramp/foo* buffer whether or not Tramp sends the line to the remote
   end.  Could you please check this?

Tramp _does_ send that line.

   Could you also check whether the command needs to be changed for
   your case to have the desired effect?

My original report concerned a remote machine running Solaris2.8.
I now tried it on a remote machine running GNU/Linux and there tramp
only inserted the 3 lines:

unset correct
unset autocorrect
exec env 'ENV=' 'PS1=$ ' /bin/sh

in .bash_history, which is still somewhat of a nuisance, but less than
hundreds, as happens on Solaris2.8.  A ~/.tramp_history file gets
created on GNU/Linux, but not on Solaris2.8.

I checked that running:

HISTFILE=~/nosuchfile
echo aha

will work (that is, create ~/nosuchfile and use it) on GNU/Linux,
whether you use sh or bash.  On Solaris2.8 it works if you use bash,
but not if you use sh.  _Maybe_ this can be considered to actually be
a bug in the Solaris2.8 version of sh, but I am not sure about that.

Sincerely,

Luc.

  reply	other threads:[~2004-05-09  1:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-02 18:43 Feature freeze and Tramp? Kai Grossjohann
2004-05-02 19:19 ` David Kastrup
2004-05-03  6:20   ` Eli Zaretskii
2004-05-03  6:03 ` Kim F. Storm
2004-05-03 14:03 ` Richard Stallman
2004-05-07 21:23 ` Kai Grossjohann
2004-05-07 22:22   ` Miles Bader
2004-05-08 10:15     ` Kai Grossjohann
2004-05-10  1:33       ` Miles Bader
2004-05-10  1:39       ` Miles Bader
2004-05-08  2:34   ` Luc Teirlinck
2004-05-08 10:34     ` Kai Grossjohann
2004-05-09  1:40       ` Luc Teirlinck [this message]
2004-05-10 13:02         ` Kai Grossjohann
2004-05-11  2:49           ` Luc Teirlinck
2004-05-11  7:08             ` Kai Grossjohann
2004-05-12  0:53               ` Luc Teirlinck
2004-05-12  1:02               ` Luc Teirlinck
2004-05-12  7:32                 ` Kai Grossjohann
2004-05-12 14:57                   ` Luc Teirlinck
2004-05-13  6:54                     ` Kai Grossjohann
2004-05-13 14:02                       ` Luc Teirlinck
2004-05-15 16:36                         ` Kai Grossjohann
2004-05-15 18:28                           ` Luc Teirlinck
2004-05-16  9:07                             ` Kai Grossjohann
2004-05-17  0:50                               ` Luc Teirlinck
2004-05-17  5:11                                 ` Kai Grossjohann
2004-05-08  3:15   ` Luc Teirlinck
2004-05-09  2:11   ` Luc Teirlinck
2004-05-09 15:35     ` Robert J. Chassell
2004-05-09 16:26       ` Luc Teirlinck
2004-05-09 20:11         ` Stefan Monnier
2004-05-10  0:08           ` Luc Teirlinck
2004-05-09  2:34   ` Luc Teirlinck
2004-05-09  2:53     ` Luc Teirlinck

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=200405090140.i491eTW28920@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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).