From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Antoine Levitt Newsgroups: gmane.emacs.devel Subject: Re: other-buffer advice on kill-buffer Date: Tue, 02 Aug 2011 02:40:49 +0200 Message-ID: <877h6w3asu.fsf@gmail.com> References: <8662mgg2ea.fsf@gmail.com> <87d3go4t4d.fsf@gmail.com> <86hb60ekx7.fsf@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1312245699 15781 80.91.229.12 (2 Aug 2011 00:41:39 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 2 Aug 2011 00:41:39 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 02 02:41:32 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Qo336-0003xb-Cc for ged-emacs-devel@m.gmane.org; Tue, 02 Aug 2011 02:41:32 +0200 Original-Received: from localhost ([::1]:35378 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qo335-0000vz-Vw for ged-emacs-devel@m.gmane.org; Mon, 01 Aug 2011 20:41:31 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:59365) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qo333-0000vp-DB for emacs-devel@gnu.org; Mon, 01 Aug 2011 20:41:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qo331-0005RP-Vd for emacs-devel@gnu.org; Mon, 01 Aug 2011 20:41:29 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:54908) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qo331-0005Qz-OF for emacs-devel@gnu.org; Mon, 01 Aug 2011 20:41:27 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Qo32y-0003ve-UI for emacs-devel@gnu.org; Tue, 02 Aug 2011 02:41:24 +0200 Original-Received: from uni14-1-82-233-220-106.fbx.proxad.net ([82.233.220.106]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Aug 2011 02:41:24 +0200 Original-Received: from antoine.levitt by uni14-1-82-233-220-106.fbx.proxad.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Aug 2011 02:41:24 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 26 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: uni14-1-82-233-220-106.fbx.proxad.net Mail-Copies-To: never User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:142656 Archived-At: 02/08/11 02:06, Jérémy Compostella > Antoine Levitt writes: >> Just out of curiosity, what buffers are you trying to exclude? > I developed an activity manager since I use Emacs as my full desktop > environment (Web, Mail, Jabber, Code with different project at the same > time). > > This activity module let me define statically and dynamically > activities. Activities are named and have open/enable/disable handlers to > modify the Emacs behavior in regards of what I like to do under a > particular activity. That seems interesting. I toyed with the idea in my mind some time ago, but couldn't figure out something neat enough to be really usable. Ideally, you'd have separate buffer groups, and C-x b with ido/iswitchb/whatever would only display the current group. There'd be a system to switch activity, with memorised window configurations, and notifications (say, ERC or gnus has received new messages, or a compilation has finished) would be unified (so you could have one keybinding to "switch to the activity requiring attention"). However, that all seems a bit hackish, and I wonder if that's not twisting emacs around too much. Your code looks cool, but I'm thinking of something a little more static - ie "c-mode or emacs-lisp-mode files under ~/emacs go to activity emacs-hack", etc.