From athas at sigkill.dk  Thu Sep  7 14:35:40 2006
From: athas at sigkill.dk (Troels Henriksen)
Date: Thu, 07 Sep 2006 16:35:40 +0200
Subject: [climacs-devel] Re: Climacs group stuff
In-Reply-To: <20060906214533.62506.qmail@web33501.mail.mud.yahoo.com> (John
	Q.'s message of "Wed, 6 Sep 2006 14:45:33 -0700 (PDT)")
References: <20060906214533.62506.qmail@web33501.mail.mud.yahoo.com>
Message-ID: <877j0fwxqb.fsf@sigkill.dk>

John Q <splittist at yahoo.com> writes:

> A couple of suggestions (sorry for doing it like this, but I'm going
> be away from my dev machine and irc for another 10 days at this
> rate):
>
> 1. Search and replace commands. Suggest new commands "Group Query
> Replace" and "Group Query Replace From Buffer" (which could
> optionally prompt for a Group) which would do the appropriate
> command on each buffer in the group in series.

This is not necessary in the current implementation - basically,
because Climacs *always* has an "active buffer" (though this is hidden
from the user) - when the user deselects the active buffer, what
actually happens is that a special group, that always designates the
current buffer, will be selected. This means that commands such as
Query Replace can elegantly be written to always act on the buffers of
the active group, which will simply be the current buffer in the case
where the user is not interested in performing group operations. Thus,
we remove the need for multiple commands that have only differences,
which means that we do not need seperate gestures for group and
non-group operations.

> (Eventually this leads to Possibilities Buffers ? la Zmacs.)

What are these? I must admit that I have never used Zmacs, the
inspiration for the group concept came from Hemlock.

> 2. System groups. Query an ASDF system for its
> component files to use as a group.

Yes! This would be very cool.

> (Also treat a file or buffer as a list of filenames/pathnames to
> establish a group; allow someone to write a TAGS file parser to get
> the names of files for a group, etc.)

This would indeed also be quite useful, yes.

-- 
\  Troels "Athas"
/\ Henriksen


From athas at sigkill.dk  Thu Sep  7 18:20:46 2006
From: athas at sigkill.dk (Troels Henriksen)
Date: Thu, 07 Sep 2006 20:20:46 +0200
Subject: [climacs-devel] Re: Climacs group stuff
In-Reply-To: <20060907155209.99026.qmail@web33502.mail.mud.yahoo.com> (John
	Q.'s message of "Thu, 7 Sep 2006 08:52:08 -0700 (PDT)")
References: <20060907155209.99026.qmail@web33502.mail.mud.yahoo.com>
Message-ID: <87y7svv8qp.fsf@sigkill.dk>

John Q <splittist at yahoo.com> writes:

> So if I have gone to the trouble of designating a
> bunch of buffers for a series of Query Replaces, and
> then want to do a Query Replace only in one of those
> buffers before continuing to work with the Group, what
> do I do?

In the current implementation, every group must have a name, so you
deselect the group, perform your operation on the current group, and
reselect the group based on its name. Perhaps this kind of operation
is common enough that a Select Previous Group command is needed?

>> > (Eventually this leads to Possibilities Buffers ?
>> la Zmacs.)
>> 
>> What are these?
>
> I've never been entirely sure myself, but I'll try to
> find a description.
>
> I've periodically been inspired by things like this
> from an old (well, 1999) Kent Pitman email
> (http://groups.google.com/group/comp.lang.lisp/msg/b2c0190dc30c3e5f?&q=zmacs+possibilities+buffer):

Wow, they sound pretty cool - the ability to pause when iterating
though the buffers of a group does not exist in the Climacs
implementation, but I can't imagine it would be too hard to
implement. I think the Climacs design of having commands automatically
operate on groups, and just having the "current buffer" as a special
group, is more elegant than using on-the-fly calculated TAGS tables,
though. :-)

-- 
\  Troels "Athas"
/\ Henriksen


From daniel_katz at post.harvard.edu  Thu Sep 14 12:42:55 2006
From: daniel_katz at post.harvard.edu (Daniel Katz)
Date: Thu, 14 Sep 2006 08:42:55 -0400
Subject: [climacs-devel] 
	Minor problem with climacs-internals.texi, and patch
Message-ID: <7DE4AAC6-CAE4-409B-AEAE-6F49F814575D@post.harvard.edu>

Hi,


I downloaded the climacs source from CVS and tried to build the  
documentation in the climacs/Doc directory.  After some processing, I  
got the following:

------------------------------------------------------------------------ 
---------------------
/Users/dkatz/programming/climacs/Doc/climacs-internals.texi:2245:  
This command
can appear only out of any environment, not in environment @deffn.
@badenverr ...temp , not @inenvironment @thisenv }

@checkenv ... at ifx @thisenv @temp @else @badenverr
                                                   @fi
@\node #1->@checkenv {}
                        @donode #1 , at finishnodeparse
l.2245 @node Index
------------------------------------------------------------------------ 
---------------------



This was a pretty trivial problem (a missing "@end deffn" for the  
define-group macro), and I got things to work with the following patch:

------------------------------------------------------------------------ 
---------------------
$ cvs diff climacs-internals.texi
Index: climacs-internals.texi
===================================================================
RCS file: /project/climacs/cvsroot/climacs/Doc/climacs-internals.texi,v
retrieving revision 1.23
diff -r1.23 climacs-internals.texi
2244a2245
 > @end deffn
------------------------------------------------------------------------ 
---------------------


I hope this is helpful.

Dan