From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: TODO Date: Tue, 26 Feb 2008 10:48:14 -0800 Message-ID: <200802261848.m1QImEag004425@sallyv1.ics.uci.edu> References: <5E2DA7EF-D0F1-4B0C-A3DC-F0B64FE2FE00@gmail.com> <13170DB6-B7A1-4843-AAF5-AB68B65D2331@gmail.com> <18370.18434.78349.822958@kahikatea.snap.net.nz> <200802261813.m1QIDEku015891@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1204051830 17857 80.91.229.12 (26 Feb 2008 18:50:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 26 Feb 2008 18:50:30 +0000 (UTC) Cc: mail.vjrao@gmail.com, emacs-devel@gnu.org, Nick Roberts , "rms@gnu.org" To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 26 19:50:55 2008 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 1JU4sh-00026i-TH for ged-emacs-devel@m.gmane.org; Tue, 26 Feb 2008 19:50:24 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JU4sC-00025i-1F for ged-emacs-devel@m.gmane.org; Tue, 26 Feb 2008 13:49:52 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JU4s7-00024m-HL for emacs-devel@gnu.org; Tue, 26 Feb 2008 13:49:47 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JU4s6-00023z-Ik for emacs-devel@gnu.org; Tue, 26 Feb 2008 13:49:46 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JU4s6-00023s-DS for emacs-devel@gnu.org; Tue, 26 Feb 2008 13:49:46 -0500 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1JU4s2-0002by-Aj; Tue, 26 Feb 2008 13:49:42 -0500 X-ICS-MailScanner-Watermark: 1204656498.37596@w61nHB1bSsLrzEMwoHN3rg Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m1QImEag004425; Tue, 26 Feb 2008 10:48:14 -0800 (PST) In-Reply-To: (Stefan Monnier's message of "Tue, 26 Feb 2008 13:26:34 -0500") Original-Lines: 42 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) 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:90520 Archived-At: Stefan Monnier writes: > >> Please let me know if anyone is already working on one of these tasks. > >> > >> ** make emacsclient accept -nw as a synonym to -t. > >> > >> ** Replace some uses of the preprocessor code in Makefile.in with the > >> equivalent autoconf. > >> > >> ** Make "emacs --daemon" start emacs without showing any frame. > >> Use emacsclient later to open frames. > > > AFAIK nobody has publicly announced that is working on any of these. > > > Do you have a copyright assignment on file? If not, it would make sense > > to get started on that as soon as possible, so that it is ready by the > > time you finish writing the code. > > > >> ** Make vc-checkin avoid reverting the buffer if has not changed after > >> the checkin. Comparing (md5 BUFFER) to (md5 FILE) should be enough. > > > I have a patch for this one. > > > But it needs a few more eyes on it from people that know the code > > involved very well to make sure it is correct and the right thing to do. > > The patch itself is not too complicated. > > BTW, I'd like someone to clarify the goal. I.e. what is it trying > to fix. It seems that if the file hasn't been changed, the current code > should at the very least end up not modifying the buffer (since > insert-file-contents already compares the bytes to find the unchanged > prefix and suffix). So what is the difference in this case between > calling revert-buffer and not calling it? The goal is not to revert the buffer after a checkin. Right now files are reverted by default after a checkin (because of the possibility that keyword expansion can change the file?). Not reverting would be good because it would keep the undo history (you probably remember that discussion). [BTW, it's quite possible that my patch is barking at the wrong tree...]