From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: Trouble with texinfo-multiple-files-update Date: Sun, 2 Jun 2013 19:16:07 +0000 Message-ID: <20130602191607.GB2765@acm.acm> References: <20130602121419.GA3401@acm.acm> <83li6szfhz.fsf@gnu.org> <20130602180532.GA2765@acm.acm> <834ndgz80i.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1370200596 13863 80.91.229.3 (2 Jun 2013 19:16:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 2 Jun 2013 19:16:36 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 02 21:16:29 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UjDlV-0006jX-Cj for ged-emacs-devel@m.gmane.org; Sun, 02 Jun 2013 21:16:29 +0200 Original-Received: from localhost ([::1]:55454 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjDlU-0002ct-SR for ged-emacs-devel@m.gmane.org; Sun, 02 Jun 2013 15:16:28 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33382) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjDlR-0002cc-5x for emacs-devel@gnu.org; Sun, 02 Jun 2013 15:16:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UjDlO-0004Ri-3s for emacs-devel@gnu.org; Sun, 02 Jun 2013 15:16:25 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:10558 helo=mail.muc.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjDlN-0004RY-Qy for emacs-devel@gnu.org; Sun, 02 Jun 2013 15:16:22 -0400 Original-Received: (qmail 94338 invoked by uid 3782); 2 Jun 2013 19:16:21 -0000 Original-Received: from acm.muc.de (p5492C92D.dip0.t-ipconnect.de [84.146.201.45]) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 02 Jun 2013 21:16:18 +0200 Original-Received: (qmail 3288 invoked by uid 1000); 2 Jun 2013 19:16:07 -0000 Content-Disposition: inline In-Reply-To: <834ndgz80i.fsf@gnu.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Delivery-Agent: TMDA/1.1.12 (Macallan) X-Primary-Address: acm@muc.de X-detected-operating-system: by eggs.gnu.org: FreeBSD 8.x X-Received-From: 193.149.48.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:160003 Archived-At: Hi, Eli. On Sun, Jun 02, 2013 at 09:23:41PM +0300, Eli Zaretskii wrote: > > Date: Sun, 2 Jun 2013 18:05:32 +0000 > > Cc: emacs-devel@gnu.org > > From: Alan Mackenzie [ .... ] > > Yes. I would prefer a command that Does One Thing And Does It Well, > > simply creating the main menu from the existing entries in the other > > files. There's no harm having an option to update those too, though. > That's what that command does: its default is to update the top-level > menu in each individual file that is part of the manual. Each file is > a full chapter. The updating of the master menu is the optional > behavior, invoked with C-u. Yes. My point is, why can't the updating of the master menu, which is a coherent action in its own right, be performed independently of updating the individual *.texi's? > > > Why do you care about the fact that they are modified? Emacs does > > > that elsewhere, e.g., when you "M-q" in a paragraph that is already > > > filled. You don't become nervous then, do you? So why here? > > I'm not so much nervous as irritated - I've got to deal with 54 > > "changed" buffers, otherwise they'll be hanging around my desktop > > forever. And I don't want to save them, since that will overwrite the > > files' timestamps. > Why do you care about files' timestamps? I just do. I find the question rather strange. Who wouldn't care about timestamps? They provide a rapid, convenient insight into the activity in the directory, in fact in any directory. For example, I see most files.texi unchanged since 2013-01-25 (when I presumably cloned the repository), and several at various points since (when I updated the repo). killing.texi hasn't been changed at all, but windows.texi was changed as recently as May. > bzr doesn't, and neither should you, because you will need to run "make > info" anyway, due to the fact that you added a node to the manual. > What am I missing? I'm not sure - I think we're talking at cross purposes, somehow. [ .... ] -- Alan Mackenzie (Nuremberg, Germany).