unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Feature change or bug - Emacs server
Date: Sat, 11 Jun 2011 05:39:43 -0500	[thread overview]
Message-ID: <87ei30k5xs.fsf@lifelogs.com> (raw)
In-Reply-To: BANLkTi=-aNGPhsCmEdSoDPD9ZKjDqsp0hw@mail.gmail.com

On Sat, 11 Jun 2011 12:48:57 +1000 Tim Cross <theophilusx@gmail.com> wrote: 

TC> Of course, if emacs had a decent web browser able to handle javascript etc
TC> and there was some way of having multiple virtual desktops, my .Xsession
TC> would likely end with something like

TC> exec emacs

TC> In the meantime, I will experiment with various wm until I find the one that
TC> is as light weight as possible while still providing all the features I
TC> want. Then I will craft my own .Xsession and hopefully again reclaim at
TC> least the feeling I know what is going on and am in control! If anyone has
TC> any recommendations on non-GNOME (or KDE for that matter) wm they have found
TC> good, I'd be i9nterested in hearing about it (possibly privately to spare
TC> the list!).

My work on Emacs as a desktop environment is exactly what you're talking
about, I think.  Look at those threads, especially
http://permalink.gmane.org/gmane.emacs.devel/139687 where I list all the
things I think are needed.  I'm just starting now, should have a usable
emacs-panel.el with functional tiles and some WM integration eventually,
and then I will add the rest gradually (help is welcome, of course).

I don't plan to replace the WM, but everything else is fair game.

Ted




  reply	other threads:[~2011-06-11 10:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  6:47 Feature change or bug - Emacs server Tim Cross
2011-06-09  7:17 ` Tassilo Horn
2011-06-09  8:13   ` chad
2011-06-09 15:21 ` Stefan Monnier
2011-06-11  2:48   ` Tim Cross
2011-06-11 10:39     ` Ted Zlatanov [this message]
2011-06-13  2:09       ` Tim Cross
2011-06-13  4:53         ` Now: Emacs<->Mozilla Integration -- Was: " Mohsen BANAN
2011-06-13  7:37           ` chad
2011-06-14  3:57             ` Tim Cross
2011-06-14  3:53           ` Tim Cross
2011-06-14  8:37           ` Daniel Colascione
2011-06-13 15:47         ` Ted Zlatanov
2011-06-14  3:42           ` Tim Cross
2011-06-14 14:53             ` Lars Magne Ingebrigtsen
2011-06-14 15:01               ` Julien Danjou
2011-06-14 17:08                 ` joakim
2011-06-14 16:17             ` Ted Zlatanov
  -- strict thread matches above, loose matches on Subject: below --
2011-06-13 16:49 T.V Raman
2011-06-13 17:11 ` Mohsen BANAN
2011-06-13 17:18 ` Ted Zlatanov
2011-06-13 17:36   ` Michael Albinus
2011-06-13 23:45   ` Antoine Levitt
2011-06-14  0:57     ` Ted Zlatanov
2011-06-14  3:12       ` Tim Cross
2011-06-14  7:49       ` Antoine Levitt
2011-06-14  9:45         ` joakim
2011-06-14  8:22       ` Michael Albinus
2011-06-13 18:31 ` joakim
2011-06-14  3:18 ` Tim Cross

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=87ei30k5xs.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).