From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: How to really clear eshell buffer? Date: Sat, 09 Jun 2018 22:02:56 +0200 Organization: Aioe.org NNTP Server Message-ID: <867en7ybgv.fsf@zoho.com> References: <39643308-1912-7c8c-88b8-e777f1b5230c@xgm.de> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1528574610 912 195.159.176.226 (9 Jun 2018 20:03:30 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 9 Jun 2018 20:03:30 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jun 09 22:03:26 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fRk54-0008Ud-Ht for geh-help-gnu-emacs@m.gmane.org; Sat, 09 Jun 2018 22:03:22 +0200 Original-Received: from localhost ([::1]:41360 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fRk7B-0003RP-De for geh-help-gnu-emacs@m.gmane.org; Sat, 09 Jun 2018 16:05:33 -0400 Original-Path: usenet.stanford.edu!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 32 Original-NNTP-Posting-Host: cRcuMnzjCdtBkcQq4LWXQQ.user.gioia.aioe.org Original-X-Complaints-To: abuse@aioe.org Cancel-Lock: sha1:rJFVVfSUWzA53ATfHmsxzOcLcMs= Mail-Copies-To: never X-Notice: Filtered by postfilter v. 0.8.3 Original-Xref: usenet.stanford.edu gnu.emacs.help:222951 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:117072 Archived-At: Bob Newell wrote: >> I want to really clear an eshell buffer, >> which means that all former output is >> deleted, not just scrolled away. > > (defun clear-eshell () > (interactive) > (setq inhibit-read-only t) > (kill-region (point-min) (point-max))) > > I don't see any real need to switch back to > read-only mode. Hit DEL and you'll see the need. (Besides it is an unexpected side effect not evident from the function name.) Second, you also kill the prompt string this way. Sure, it returns with RET, but this isn't how one would expect clear to work. It should, IMO, work just like in a VT with the state unchanged WRT read-only, and with the prompt intact, only the material removed! Thrid, with `kill-region', the material ends up in the kill ring. Unclear if this is intuitive or not? -- underground experts united http://user.it.uu.se/~embe8573