From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: A wish, a plea Date: Fri, 22 Jun 2007 15:57:48 +0300 Message-ID: References: <4679F561.4030600@hacksaw.org> <87d4zomyiw.fsf@red-bean.com> <87fy4kjy0k.fsf@red-bean.com> <467AF6CC.2000300@gnu.org> <86ejk4jtno.fsf@lola.quinscape.zz> <877ipwqtg9.fsf@red-bean.com> <86ejk4i2gn.fsf@lola.quinscape.zz> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: sea.gmane.org 1182517095 32303 80.91.229.12 (22 Jun 2007 12:58:15 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 22 Jun 2007 12:58:15 +0000 (UTC) Cc: wilde@sha-bang.de, hacksaw@hacksaw.org, emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 22 14:58:13 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1I1iiI-0008Ep-40 for ged-emacs-devel@m.gmane.org; Fri, 22 Jun 2007 14:58:10 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I1iiH-0000TX-NC for ged-emacs-devel@m.gmane.org; Fri, 22 Jun 2007 08:58:09 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I1iiD-0000Pd-8V for emacs-devel@gnu.org; Fri, 22 Jun 2007 08:58:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I1iiA-0000Nm-PW for emacs-devel@gnu.org; Fri, 22 Jun 2007 08:58:03 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I1iiA-0000Nj-Jb for emacs-devel@gnu.org; Fri, 22 Jun 2007 08:58:02 -0400 Original-Received: from nitzan.inter.net.il ([213.8.233.22]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I1ii9-0006My-Ca; Fri, 22 Jun 2007 08:58:01 -0400 Original-Received: from HOME-C4E4A596F7 ([81.5.57.90]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id HBA29216 (AUTH halo1); Fri, 22 Jun 2007 15:57:53 +0300 (IDT) In-reply-to: <86ejk4i2gn.fsf@lola.quinscape.zz> (message from David Kastrup on Fri, 22 Jun 2007 14:43:52 +0200) X-detected-kernel: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:73616 Archived-At: > Cc: Karl Fogel , wilde@sha-bang.de, emacs-devel@gnu.org, > hacksaw@hacksaw.org > From: David Kastrup > Date: Fri, 22 Jun 2007 14:43:52 +0200 > > > It sounds awful to me. It reminds me Notepad and Word with their > > pesky UNNAMED and DOCUMENT1 defaults. > > Being reminded of Notepad and Word is not in itself good or bad. > Could you explain where the peskiness lies? I don't like software that decides for me whether I do or don't want to write a document, and on top of that decides what would be the name of that file. > > Did anyone in this longish thread suggest to simply turn on > > auto-save in *scratch*, like we do in *mail* buffers? If not, would > > that solve the OP's problem without any significant nasty side > > effects? > > Uh, it has the nasty side effect of starting to write to my disk > without asking my confirmation. The same happens in *mail* buffers. How is this case different? > If I have started several Emacs > instances, I don't want them complaining about file locks and similar > nonsense just because I use the *scratch* buffer in both. Did you actually try that in *scratch*? I don't think there will be any locks, since I didn't suggest to give the buffer an associated file, just to turn on auto-save in it. That's a different thing. > I don't really think that *scratch* should usually be associated with > any file. That's not what I suggested. I suggested the equivalent of (auto-save-mode 1)