From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Evans Winner Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.60; org-mode missing from fresh cvs Emacs? Date: Thu, 27 Mar 2008 21:37:03 -0600 Message-ID: <861w5v1puo.fsf@timbral.net> References: <20080327140507.A1A9B1B4CF@mail.timbral.net> <86skyberao.fsf@timbral.net> <47EC2380.3000107@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1206675923 15400 80.91.229.12 (28 Mar 2008 03:45:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 28 Mar 2008 03:45:23 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 28 04:45:54 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 1Jf5XG-0003XV-NJ for ged-emacs-devel@m.gmane.org; Fri, 28 Mar 2008 04:45:47 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jf5Wf-0006yk-4X for ged-emacs-devel@m.gmane.org; Thu, 27 Mar 2008 23:45:09 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jf5Wb-0006yG-JZ for emacs-devel@gnu.org; Thu, 27 Mar 2008 23:45:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jf5Wa-0006xz-Jg for emacs-devel@gnu.org; Thu, 27 Mar 2008 23:45:04 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jf5Wa-0006xv-C3 for emacs-devel@gnu.org; Thu, 27 Mar 2008 23:45:04 -0400 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jf5Wa-0004ee-1o for emacs-devel@gnu.org; Thu, 27 Mar 2008 23:45:04 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Jf5WQ-0003Ir-Ja for emacs-devel@gnu.org; Fri, 28 Mar 2008 03:44:54 +0000 Original-Received: from 67.42.142.120 ([67.42.142.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Mar 2008 03:44:54 +0000 Original-Received: from thorne by 67.42.142.120 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Mar 2008 03:44:54 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 26 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 67.42.142.120 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:qkQZeoZdu/XqkKk0EYgF3gcD7zU= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:93682 gmane.emacs.pretest.bugs:21737 Archived-At: Jason Rumney writes: Evans Winner wrote: >> I do see lisp/org both in my source directory and in >> /usr/local/share/emacs/23.0.60/ now. ./configure was >> run without any args, which always worked okay in the >> past. Then ``make maintainer-clean'' (based on >> another thread) and ``make bootstrap''. Any idea >> what I should look at? subdirs.el perhaps? Does it not get updated by a bootstrap? This problem mysteriously went away. But it might have to do with a misunderstanding on my part about the multi-tty feature. If there is an Emacs running on the X console at home and I connect with ssh I thought I had to use `emacsclient' to connect to it. But if I do `emacs' will that connect me to the existing session? Because when I got home I found a session I thought had died yesterday was still running. So, it may be that when I was testing the new build this afternoon from work I was really connecting to the old build that had the problem...? Seems unlikely that I would have not realized it, but it's all I can think of. Anyway, the problem is gone now, and thanks for the help.