cons-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How do I inhibit the copying of the source files to the build tree


From: Doug Alcorn
Subject: Re: How do I inhibit the copying of the source files to the build tree
Date: 15 Mar 2002 10:20:45 -0500
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)

Timothee Besset <address@hidden> writes:

> The other solution is to live in an open source world and be able to
> patch your IDE code to understand some basic things about
> cons. Probably not relevant to you, but I am working on patches for
> Anjuta (http://anjuta.sourceforge.net, a unix/Linux IDE) to teach it
> how to deal with linked dirs and open the 'real' files instead.

It's not really as easy as this.  On Unix/Linux cons uses hard links.
Symlinks have the concept of a "real" and "not-real" directory entry.
Hard links do not.  When looking at filenames and an inode it is
impossible to know which filename is the "first" or "original".

IMO, the best thing to do is have your IDE track the actual inode
number for all of its open files.  Then it will know if a new
file-open request is for one of its existing buffers.  Instead of
opening the hard link it just redisplays the same buffer for the
already open inode.  You can even relabel the second copy of the
buffer but leave them linked (I think this is what vim does).

Anyway, this is a personal pet peeve of mine.  I bring it up on the
list every so often.  I think there are some work arounds for xemacs
(what I use), I just haven't been able to get any of them to work.
-- 
 (__) Doug Alcorn (mailto:address@hidden http://www.lathi.net)
 oo / PGP 02B3 1E26 BCF2 9AAF 93F1  61D7 450C B264 3E63 D543
 |_/  If you're a capitalist and you have the best goods and they're
      free, you don't have to proselytize, you just have to wait. 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]