From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Ludwig, Mark" Newsgroups: gmane.emacs.help Subject: RE: Switching branches and TAB Date: Thu, 30 May 2013 22:59:48 +0000 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1369954810 13820 80.91.229.3 (30 May 2013 23:00:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 30 May 2013 23:00:10 +0000 (UTC) To: Barry OReilly , help-gnu-emacs Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri May 31 01:00:09 2013 Return-path: Envelope-to: geh-help-gnu-emacs@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 1UiBpJ-0004F9-By for geh-help-gnu-emacs@m.gmane.org; Fri, 31 May 2013 01:00:09 +0200 Original-Received: from localhost ([::1]:49863 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UiBpJ-0007T5-2v for geh-help-gnu-emacs@m.gmane.org; Thu, 30 May 2013 19:00:09 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34363) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UiBp4-0007ST-Rw for help-gnu-emacs@gnu.org; Thu, 30 May 2013 18:59:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UiBp3-0006rr-Qa for help-gnu-emacs@gnu.org; Thu, 30 May 2013 18:59:54 -0400 Original-Received: from usslmhub002.ugs.com ([134.244.32.85]:51910 helo=ugs.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UiBp3-0006rj-JS for help-gnu-emacs@gnu.org; Thu, 30 May 2013 18:59:53 -0400 Original-Received: from USSLMMBX002.net.plm.eds.com (161.134.138.62) by USSLMHUB002.net.plm.eds.com (134.244.32.85) with Microsoft SMTP Server (TLS) id 14.2.318.1; Thu, 30 May 2013 17:59:50 -0500 Original-Received: from USSLMMBX003.net.plm.eds.com ([169.254.2.229]) by USSLMMBX002.net.plm.eds.com ([169.254.1.184]) with mapi id 14.02.0318.001; Thu, 30 May 2013 17:59:50 -0500 Thread-Topic: Switching branches and TAB Thread-Index: AQHOXW6JTSeZZzQzNEKcBT1p1AsV75keRd2g In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [146.122.225.251] X-detected-operating-system: by eggs.gnu.org: Windows 7 or 8 X-Received-From: 134.244.32.85 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:91187 Archived-At: > From: Barry OReilly, Thursday, May 30, 2013 2:48 PM >=20 > > I am using ClearCase as a source control and emacs for eshell. If I pic= k > a view > > (similar to changing branches) before launching emacs&, when I am typin= g > a file > > path in eshell, i can press tab to finish the path name for folders and > files. > > However, if i launch emacs& and then set the view, the ability to press > tab to > > finsih the path name does not work for some files. This also occurs whe= n > > setting to a different view in eshell. > > > > So whenever I would want to change views, I could start up a new emacs& > to > > avoid this problem. Is there someway around doing this? >=20 > I'm also in the unfortunate position of using that atrocity of a VCS. >=20 > When you set dynamic view, a new csh-like shell is started. If you starte= d > Emacs before that, it forked from the parent shell so has no visibility o= f > the new shell. You could run xterm&, set view, switch to the new xterm an= d > find you won't see your view's files for the same reason. >=20 > I wouldn't expect any issue in snapshot views. I also use ClearCase, frequently have several dynamic views open concurrently, and may have an instance of Emacs for each. In my case, this feels natural, because I have a complete context in the view, so it feels natural to have a unique instance of Emacs in that view too. For example, I frequently run hours-long builds ("compiles") concurrently in these instances of Emacs. One instance couldn't do that (only one "*compilation*" buffer without more customization than I feel would be good to do, not to mention losing everything if that one=20 Emacs were to crash). It probably helps that the way we refer to files involves environmental variables (one per "module" of this large software system), each of which having a definition starting with /vobs/.... Sure, I can use /view/foo/vobs/... when I need to work across views, but I rarely need to do that. In a real sense, each view represents a "project" I'm working on. At the moment, I have 18 views active (each in its own xterm) with 12 instances of Emacs running (not running Emacs in 6 views). [[ I find ClearCase more powerful than most other source code management systems. This could be because of the customization we have that manages queues of sets of changes -- dozens of queues, one for each of the multiple releases of the products and each of the customer-specific maintenance versions that we concurrently maintain. It uses a hierarchy among all of these with a good deal of automation around merging. The semi-automated merging makes sets of changes flow among the queues, making it easy for the engineers to remember to propagate changes in the "forward" direction among releases until hitting the end. Along with the formalized review process before leaving a queue, this helps ensure that customer-specific maintenance gets generalized and incorporated into the "latest and greatest" version of the product. Each of my personal views has an associated branch where I do my project work, and for our concurrent development on half a dozen platforms, I use up to half a dozen different views per branch for each platform's build of that branch (if there is platform-specific stuff I need to worry about, or if I want some particular compiler's scrutiny such as using GCC on Linux for its ability to warn when printf-style format strings aren't matched with the data arguments). ]] Cheers, Mark