From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Luc Teirlinck Newsgroups: gmane.emacs.devel Subject: Re: Feature freeze and Tramp? Date: Wed, 12 May 2004 09:57:08 -0500 (CDT) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <200405121457.i4CEv8D15723@raven.dms.auburn.edu> References: <87zn8qlleb.fsf@emptyhost.emptydomain.de> <87d65gj5j2.fsf@emptyhost.emptydomain.de> <200405080234.i482YKE24109@raven.dms.auburn.edu> <87wu3n4380.fsf@emptyhost.emptydomain.de> <200405090140.i491eTW28920@raven.dms.auburn.edu> <87n04gzb7h.fsf@emptyhost.emptydomain.de> <200405110249.i4B2nND22278@raven.dms.auburn.edu> <87sme7o2zu.fsf@emptyhost.emptydomain.de> <200405120102.i4C127e12749@raven.dms.auburn.edu> <8765b2ksm7.fsf@emptyhost.emptydomain.de> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1084375450 25273 80.91.224.253 (12 May 2004 15:24:10 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 12 May 2004 15:24:10 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed May 12 17:23:57 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNvaP-0002z6-00 for ; Wed, 12 May 2004 17:23:57 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNvaP-00010D-00 for ; Wed, 12 May 2004 17:23:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNvBk-0003KA-W2 for emacs-devel@quimby.gnus.org; Wed, 12 May 2004 10:58:29 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BNvB7-0003GP-PZ for emacs-devel@gnu.org; Wed, 12 May 2004 10:57:49 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BNvAa-00036u-3n for emacs-devel@gnu.org; Wed, 12 May 2004 10:57:47 -0400 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNvAZ-00036c-Po for emacs-devel@gnu.org; Wed, 12 May 2004 10:57:15 -0400 Original-Received: from raven.dms.auburn.edu (raven.dms.auburn.edu [131.204.53.29]) by manatee.dms.auburn.edu (8.12.10/8.12.10) with ESMTP id i4CEvDTS008574; Wed, 12 May 2004 09:57:13 -0500 (CDT) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.6+Sun/8.11.6) id i4CEv8D15723; Wed, 12 May 2004 09:57:08 -0500 (CDT) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: kai@emptydomain.de In-reply-to: <8765b2ksm7.fsf@emptyhost.emptydomain.de> (message from Kai Grossjohann on Wed, 12 May 2004 09:32:48 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23252 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23252 Kai Grossjohann wrote: * tramp.el (tramp-open-connection-setup-interactive-shell): `unset HISTFILE' rather than `set -o history' to turn off the history. Is `set -o history' a typo? In my version of bash that turns _on_ history and I have to use `set +o history' to turn it off. Anyway, this feature indeed seems to be bash-specific and hence useless if you do not know that the shell is bash. `unset HISTFILE' would not work at the particular spot anyway, even if the shell is bash, because one has to export the "history-disabledness" and "unsettedness" of variables does not get exported. * tramp.el (tramp-open-connection-setup-interactive-shell): Posix shells don't allow you to turn off the history, so we redirect it to an innocuous file and limits that file's size as much as possible. They certainly do not allow `set +o history'. After `bash --posix', both `unset HISTFILE' and `HISTFILE=' seem to work. But the fact that they work in `bash --posix' is definitely no "proof". Maybe some other shells insist on using their default history file if HISTFILE is either unset _or_ null, so it probably is safer to keep the current constructs. Sincerely, Luc.