From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: emacs for everything?
Date: Wed, 01 Dec 2004 17:34:17 +0100 [thread overview]
Message-ID: <86u0r69dva.fsf@ketchup.de.uu.net> (raw)
In-Reply-To: 87y8gkr8p1.fld@barrow.com
floyd@barrow.com (Floyd L. Davidson) writes:
> Regardless of tabs though, I find the discussion of different
> ways to approach screen management are very useful as a way to
> develop new ideas.
That is highly true!
You suggested to use more workspaces. I tend to restrict myself to
fewer workspaces, each of them with a predefined role. One workspace
is for communication (contains an Emacs instance dedicated to Gnus
plus Gaim plus an xterm for miscellaneous stuff), another is for doing
sw development (contains my other Emacs instance and an xterm, another
is for browsing the web (contains Firefox and Acroread and
OpenOffice -- OOo isn't used for browsing the web but I didn't know
where else to put it), and a couple of others are for in-house
applications I use, one app per workspace. (These apps aren't usable
in anything but fullscreen mode.)
So basically my division of workspaces goes by program type, not by
project.
It could be quite useful to use workspaces according to project. (For
the right value of "project" ;-)
Hm. At one point, I did use one of my spare workspaces for a specific
task: for testing a web application. So I created another Firefox
window and an xterm, tail -f'd the right logfile in the xterm, and
clicked away in Firefox to see what would happen. That was a good
experience. However, I can't seem to get myself to using workspaces
that way.
Do you allocate workspaces dynamically, or are they more or less
static? That is, do you always have the same set of projects and do
you always know which project will be in which workspace? Or do you
use the same workspace for one project today and for another tomorrow?
Hm. Ion supports the dynamic workspace allocation well: it allows you
to enter a name, then it creates a workspace by that name. And you
can select a workspace by name. This means that if you always use the
project name as workspace name, then it doesn't matter which set of
projects you happen to work on today.
Kai
next prev parent reply other threads:[~2004-12-01 16:34 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 5:41 emacs for everything? Joe Corneli
[not found] ` <mailman.3197.1100662500.8225.help-gnu-emacs@gnu.org>
2004-11-16 11:58 ` Fabian Braennstroem
2004-11-17 19:05 ` Floyd L. Davidson
2004-11-20 17:19 ` Kai Grossjohann
2004-11-21 9:17 ` Janusz S. Bień
[not found] ` <mailman.363.1101029322.27204.help-gnu-emacs@gnu.org>
2004-12-05 1:23 ` Zajcev Evgeny
[not found] ` <mailman.236.1100971735.27204.help-gnu-emacs@gnu.org>
2004-11-20 18:18 ` Pascal Bourguignon
2004-11-20 21:40 ` Jay Belanger
2004-11-20 23:05 ` Alan Mackenzie
2004-11-21 9:29 ` Joe Corneli
2004-11-21 16:22 ` Pascal Bourguignon
2004-11-20 18:45 ` Floyd L. Davidson
2004-11-22 10:27 ` Kai Grossjohann
2004-11-22 13:50 ` John Sullivan
2004-11-23 19:57 ` Maciek Pasternacki
2004-11-25 13:31 ` Kai Grossjohann
2004-11-25 14:52 ` Maciek Pasternacki
2004-11-26 9:03 ` Kai Grossjohann
2004-11-27 17:12 ` Maciek Pasternacki
2004-11-27 19:50 ` Kai Grossjohann
2004-11-28 1:29 ` Maciek Pasternacki
2004-11-28 11:47 ` Kai Grossjohann
2004-11-27 23:16 ` Daniel Pittman
[not found] ` <mailman.1437.1101390082.27204.help-gnu-emacs@gnu.org>
2004-11-25 15:19 ` Mike
2004-11-25 15:45 ` Maciek Pasternacki
[not found] ` <mailman.1058.1101240531.27204.help-gnu-emacs@gnu.org>
2004-11-24 4:13 ` Lee Sau Dan
2004-11-24 13:10 ` Maciek Pasternacki
2004-11-24 14:25 ` Leonardo Boiko
2004-11-24 20:33 ` Maciek Pasternacki
2004-11-24 20:49 ` Leonardo Boiko
[not found] ` <mailman.1312.1101329987.27204.help-gnu-emacs@gnu.org>
2004-12-01 17:49 ` Kevin Rodgers
[not found] ` <mailman.1308.1101329036.27204.help-gnu-emacs@gnu.org>
2004-11-25 3:16 ` Pascal Bourguignon
2004-11-25 13:16 ` Maciek Pasternacki
[not found] ` <mailman.1434.1101389211.27204.help-gnu-emacs@gnu.org>
2004-11-25 20:12 ` Stefan Monnier
2004-11-25 21:03 ` Maciek Pasternacki
[not found] ` <mailman.1503.1101417224.27204.help-gnu-emacs@gnu.org>
2004-11-27 22:00 ` Stefan Monnier
2004-11-28 1:31 ` Maciek Pasternacki
2004-11-25 17:06 ` Mathias Dahl
2004-11-28 14:29 ` Lee Sau Dan
2004-11-28 20:24 ` Joe Corneli
2004-11-30 10:00 ` ken
[not found] ` <mailman.591.1101120112.27204.help-gnu-emacs@gnu.org>
2004-11-24 23:58 ` Floyd L. Davidson
2004-11-27 20:07 ` Kai Grossjohann
2004-11-27 23:08 ` Micha Feigin
2004-11-28 1:33 ` Maciek Pasternacki
[not found] ` <mailman.1945.1101634177.27204.help-gnu-emacs@gnu.org>
2004-11-28 12:24 ` Floyd L. Davidson
2004-11-29 11:56 ` Kai Grossjohann
[not found] ` <mailman.2151.1101729999.27204.help-gnu-emacs@gnu.org>
2004-11-29 15:11 ` Floyd L. Davidson
2004-12-01 16:34 ` Kai Grossjohann [this message]
[not found] ` <mailman.2811.1101919485.27204.help-gnu-emacs@gnu.org>
2004-12-03 19:55 ` Floyd L. Davidson
[not found] ` <mailman.1836.1101586658.27204.help-gnu-emacs@gnu.org>
2004-11-27 22:00 ` Floyd L. Davidson
2004-11-28 18:36 ` David Hansen
2004-11-30 10:15 ` dual head video system (was Re: emacs for everything?) ken
[not found] ` <mailman.2423.1101810331.27204.help-gnu-emacs@gnu.org>
2004-11-30 13:01 ` dual head video system Floyd L. Davidson
2004-11-18 19:47 ` emacs for everything? Alan Mackenzie
2004-11-17 20:50 ` Alan Mackenzie
2004-11-17 22:46 ` Joe Corneli
[not found] ` <mailman.3419.1100732160.8225.help-gnu-emacs@gnu.org>
2004-11-18 19:42 ` Alan Mackenzie
2004-11-18 22:41 ` Joe Corneli
2004-11-17 3:24 ` Joe Corneli
[not found] <mailman.2999.1100584262.8225.help-gnu-emacs@gnu.org>
2004-12-06 2:44 ` David Combs
2004-12-06 4:11 ` Pascal Bourguignon
2004-12-27 1:59 ` David Combs
2004-12-30 7:04 ` Ravi Uday
2004-12-30 7:30 ` Neon Absentius
[not found] ` <mailman.9951.1104392583.27204.help-gnu-emacs@gnu.org>
2004-12-30 9:32 ` Ravi Uday
2004-12-30 9:53 ` Christian Plate
2004-12-30 9:59 ` Neon Absentius
2004-12-30 10:17 ` Peter Dyballa
2004-12-30 12:25 ` kurtz
2004-12-30 15:11 ` Floyd L. Davidson
2004-12-30 15:27 ` David Kastrup
2004-12-30 16:33 ` Floyd L. Davidson
2004-12-30 16:39 ` David Kastrup
-- strict thread matches above, loose matches on Subject: below --
2004-11-15 1:29 Mike
2004-11-15 2:30 ` Henrik S. Hansen
2004-11-15 14:52 ` Per Abrahamsen
2004-11-15 16:32 ` Henrik S. Hansen
2004-11-16 10:09 ` William Xuuu
2004-11-16 13:20 ` Floyd L. Davidson
2004-11-16 20:07 ` Alan Mackenzie
2004-11-17 13:22 ` Oliver Scholz
2004-11-17 15:30 ` Thien-Thi Nguyen
2004-11-17 18:45 ` Floyd L. Davidson
2004-11-17 20:11 ` Thien-Thi Nguyen
2004-11-17 22:07 ` Henrik S. Hansen
2004-11-18 18:51 ` Alan Mackenzie
2004-11-18 22:03 ` Stefan Monnier
2004-11-19 0:48 ` Floyd L. Davidson
2004-11-19 19:41 ` Alan Mackenzie
2004-11-19 19:00 ` Cristian Gutierrez
2004-11-19 20:29 ` Leonardo Boiko
2004-11-26 4:51 ` William Xuuu
2004-11-23 12:27 ` Alex Polite
2004-12-06 2:39 ` David Combs
2004-11-15 2:51 ` V. L. Simpson
2004-11-15 3:03 ` David Hansen
2004-11-15 3:17 ` Galen Boyer
2004-11-15 7:06 ` Kin Cho
2004-11-16 1:57 ` Joe Fineman
2004-11-15 7:37 ` Gian Uberto Lauri
2004-11-15 12:56 ` Pascal Bourguignon
2004-11-15 13:09 ` respower
2004-11-15 14:37 ` Thien-Thi Nguyen
2004-11-17 13:27 ` Oliver Scholz
2004-11-16 11:00 ` Kai Grossjohann
[not found] ` <mailman.3054.1100603433.8225.help-gnu-emacs@gnu.org>
2004-11-16 15:41 ` Mathias Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86u0r69dva.fsf@ketchup.de.uu.net \
--to=kai@emptydomain.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).