Re: emacs for everything?

[Kai Grossjohann]

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