From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Scratch buffer annoyance Date: Wed, 1 Aug 2007 07:32:44 -0700 Message-ID: References: <864pjjpuhn.fsf@lola.quinscape.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1185978861 26935 80.91.229.12 (1 Aug 2007 14:34:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 1 Aug 2007 14:34:21 +0000 (UTC) To: Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 01 16:34:15 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 1IGFHB-0001Zd-MU for ged-emacs-devel@m.gmane.org; Wed, 01 Aug 2007 16:34:13 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IGFHB-0001Qa-4q for ged-emacs-devel@m.gmane.org; Wed, 01 Aug 2007 10:34:13 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IGFH7-0001PT-UT for emacs-devel@gnu.org; Wed, 01 Aug 2007 10:34:09 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IGFH7-0001PE-9I for emacs-devel@gnu.org; Wed, 01 Aug 2007 10:34:09 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IGFH7-0001PB-64 for emacs-devel@gnu.org; Wed, 01 Aug 2007 10:34:09 -0400 Original-Received: from rgminet01.oracle.com ([148.87.113.118]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IGFH6-0003Z3-JG for emacs-devel@gnu.org; Wed, 01 Aug 2007 10:34:08 -0400 Original-Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id l71EY5G2012377 for ; Wed, 1 Aug 2007 08:34:06 -0600 Original-Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id l71CsPgB009688 for ; Wed, 1 Aug 2007 08:34:05 -0600 Original-Received: from dhcp-amer-whq-csvpn-gw3-141-144-84-209.vpn.oracle.com by acsmt350.oracle.com with ESMTP id 3084775531185978772; Wed, 01 Aug 2007 07:32:52 -0700 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <864pjjpuhn.fsf@lola.quinscape.zz> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-Detected-Kernel: Linux 2.4-2.6 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:75907 Archived-At: > > If the string value of the option names a file or directory, then > > visit it. > > You mean, if the name is "*scratch*" and in the current directory > at the time the desktop finished loading, there exists a file named > "*scratch*", this should be visited? So require the file and directory names to be absolute names. > And if the current directory at the time of the startup happens to be > "/dak@fencepost.gnu.org:/home/g/gnudist" because there was the last > file loaded, then it should go through a remote connection and check > for the existence of "*scratch*" there? Require an absolute file name. [Or tell users that they take a chance if they use a relative name.] > > > ...any number of buffers might be loaded already... > > > > If not, and if the value names one of those numerous buffers "loaded > > already" (do we "load" buffers, BTW?), > > No. Files are visited by loading them into buffers. See how easy it is to use terms loosely? I said "visit" a buffer; you said "load" a buffer. Let us both do penance ;-). > > then display and select it. If not, and the value is a string, > > create, display, and select a buffer with that name. > > > >> Those numbers in general _don't_ have a buffer name corresponding to an > >> actual complete file name (there certainly won't be a buffer named ~/ > >> even if ~/ is already visited at the time the splash screen might get > >> displayed). > > > > And? If the string value is "~/", then visit the home directory. > > You have provided no coherent logic that would have this effect > without a lot of drawbacks. Don't know what that means. What is the problem with interpreting "~/" as an absolute directory name (after expansion of `~')? Please elaborate on "a lot of drawbacks". > > If the string names an existing buffer, then display and select it; > > if not, create, display, and select a buffer with that name. Why > > would such a buffer need to "have a buffer name corresponding to an > > actual complete file name"? > > Because visiting a random file depending on just where we are at > startup is not useful behavior. It's not random if its address is provided by the user as the option value.