Years ago I loved Apollo workstations' DM (Display Manager).  Ever
since becoming an emacs user I have dreamed of recreating that
environment.  The emergence of robust tiling window managers and the
example of Drew Adams' OneOnOne package
(http://www.emacswiki.org/emacs/OneOnOneEmacs) leads me to believe
that after a couple decades the dream may now be close to realization.

For reference my present environment is Ubuntu Jaunty.  Under
Gnome/Metacity I have emacs-snapshot (23.0.92.1) more or less working
in the the single mini-buffer for all frames mode.  The mini-buffer
frame is positioned at the bottom of the screen immediately above
Gnome's bottom panel and full-screen wide.

Now I am playing with awesome.  Emacs' various frames show up but only
in a fairly chaotic fashion with the mini-buffer tossed in (not that I
expected anything different).  My next step is to get awesome to
handle the mini-buffer properly.  I am a C/C++ programmer by trade and
expect to learn Lua before I'm done.  So I am not looking for
solutions on a sliver platter but general guidance before I embark
will be much appreciated.

Let me describe the behavior I desire and hopefully readers will be
able to suggest one or more lines of attack.  (In the following I use
the term 'frame' in the Emacs sense.)

1) The mini-buffer frame should be present in any tag that contains at
least one (non-mini-buffer) Emacs frame.

2) The mini-buffer frame should occupy space at the bottom of the
screen, much like a panel or tray.  This space should no more be
available to the layout functions than the space occupied by the
awesome top bar.

3) Under some conditions the mini-buffer frame's height may increase
briefly.  In this case the mini-buffer frame should remain anchored to
the bottom of the screen.  The portion of the mini0buffer frame
exceeding the basic reserved space should behave as if it were
floating.  That is, rather than cause a re-layout it should simply
overlay the other clients.

Thanks in advance,

/john

-- 
To unsubscribe, send mail to [email protected].

Reply via email to