From: Samuel El-Borai <samuel.elborai@gmail.com>
To: Feng Shu <tumashu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs as WM
Date: Mon, 11 Aug 2014 10:19:53 +0200 [thread overview]
Message-ID: <CAFn2JfmHQRf1xi=0ub09Jod2zjw-zUG6mEQ20XmAsk1=dUGGLA@mail.gmail.com> (raw)
In-Reply-To: <87zjfe1t3y.fsf@news.tumashu-localhost.org>
[-- Attachment #1: Type: text/plain, Size: 4262 bytes --]
Other projects of the same kind:
Guile-WM (Guile scheme)
-------------------------------------
From the README:
"Guile-WM is a framework for creating an X window manager (or any other
X
application, really) and a set of useful modules designed for that purpose.
[...]
Guile-WM relies /heavily/ on its user init file. In fact, it won't
do anything on
its own without one. The intention is to provide something 100%
configurable."
Link: https://github.com/mwitmer/guile-wm
# The Deep Space Window Manager (Common Lisp)
From the README:
"DSWM is a fork of StumpWM, so have most of all features, which have
StumpWM, but it designed for better usability and better integration with
emacs."
Link: https://github.com/dss-project/dswm
You can also read a discussion about those here:
https://news.ycombinator.com/item?id=8160968
2014-08-09 1:04 GMT+02:00 Feng Shu <tumashu@gmail.com>:
> John Yates <john@yates-sheets.org> writes:
>
> > Personally I regularly have the opposite itch: wanting to replace
> > emacs's frustrating window management with an external tiling WM (in
> > my case awesome).
>
> I use stumpwm, which is like emacs.
>
> >
> > /john
> >
> > On Fri, Aug 8, 2014 at 4:35 PM, Matthew Plant <maplant2@illinois.edu>
> > wrote:
> >
> > I was curious about what people on this list thought about
> > application
> > embedding in Emacs. To a degree this is already supported with
> > ansi
> > term, but this obviously doesn't extend to GUI applications. For
> > those
> > of you familiar with Plan 9, think of how programs use the window
> > the
> > terminal they're launched in; embedding GUI apps in Emacs would
> > force
> > the program to run in a window owned by Emacs and fitted into a
> > buffer.
> >
> > The reason why I bring this up is because it would be relatively
> > easy to
> > do in a way that's not very platform agnostic. It's really easy to
> > replace the X libarary (forgive me for not using proper
> > nomenclature;
> > it'd lengthen this email tenfold) window creation functions with
> > one
> > that extends contol over the window. The degree of integration can
> > be
> > controlled by the number of replaced functions. If drawn text
> > wants to
> > be handled specially, those functions would be replaced. Some
> > method can
> > be specified for switching between emacs and the application
> > controlling
> > user input.
> >
> > This has some obvious advantages; for one, Emacs automatically
> > subsumes
> > all editors, including more WYSIWYG editors. Not only that, but
> > Emacs
> > essentially becomes a window manager, which I personally would
> > love. Because some apps, particular web browsers, do not always
> > require
> > special handling of the keyboard, switching between regular Emacs
> > buffers and the special app buffers would be generally seamless. I
> > could
> > imagine myself typing away in one Emacs buffer, momentarily moving
> > to
> > the mouse to click throught some online doxygen in my web browser
> > in the
> > buffer to the right.
> >
> > There are also a lot of disadvantages to this. For one, the
> > applications
> > would be pretty buggy without some effort to re-implement X
> > functions. Also, my co-worker points out that this would be
> > incongrous
> > with the current capabilities of Emacs, one of which is the easy
> > transfer of text betwixt buffers. Getting these two features to
> > work
> > harmoniously would be kind of difficult; lots of wrappers to
> > X/Gnome/whatever text writing functions would have to be made.
> > However,
> > copy and paste would work (I'm guessing) out of the box.
> >
> > I suppose it all boils down to what people want with the future of
> > Emacs. Personally, I would love to turn on my computer and have
> > Emacs be
> > there every step of the way. I genuinely think that Emacs is a
> > great
> > full interface to an OS. It is not a full OS however and never
> > should
> > be, which is why I like this idea as an in-between.
> >
> > -M
>
> --
>
>
>
[-- Attachment #2: Type: text/html, Size: 7837 bytes --]
next prev parent reply other threads:[~2014-08-11 8:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 20:35 Emacs as WM Matthew Plant
2014-08-08 20:51 ` John Yates
2014-08-08 23:04 ` Feng Shu
2014-08-11 8:19 ` Samuel El-Borai [this message]
2014-08-08 22:49 ` joakim
2014-08-11 1:44 ` Richard Stallman
2014-08-11 7:33 ` document sharing (was Re: Emacs as WM) Nic Ferrier
2014-08-11 14:36 ` Emacs as WM Stefan Monnier
2014-08-12 3:15 ` Richard Stallman
2014-08-12 13:59 ` Stefan Monnier
2014-08-13 3:58 ` Richard Stallman
2014-08-13 12:53 ` Stefan Monnier
2014-08-13 22:48 ` Richard Stallman
2014-08-14 2:43 ` Matthew Plant
2014-08-15 1:03 ` Richard Stallman
2014-08-15 2:59 ` Stefan Monnier
2014-08-15 17:48 ` Richard Stallman
2014-08-15 19:08 ` Stefan Monnier
2014-08-16 2:19 ` Matthew Plant
2014-08-16 3:06 ` Richard Stallman
2014-08-17 14:47 ` Ashton Kemerling
2014-08-18 1:07 ` Richard Stallman
2014-08-18 2:39 ` andres.ramirez
2014-08-18 14:41 ` Eli Zaretskii
2014-08-18 20:13 ` andres.ramirez
2014-08-18 20:54 ` Glenn Morris
2014-08-19 1:04 ` Ashton Kemerling
2014-08-19 2:45 ` Eli Zaretskii
2014-08-19 4:56 ` Ashton Kemerling
2014-08-19 5:58 ` Tom
2014-08-19 14:56 ` Eli Zaretskii
2014-08-19 15:21 ` Tom
2014-08-19 15:39 ` Eli Zaretskii
2014-08-19 15:48 ` David Kastrup
2014-08-19 13:09 ` Richard Stallman
2014-08-20 1:55 ` Alexis
2014-08-20 2:16 ` andres.ramirez
2014-08-21 2:41 ` Richard Stallman
2014-08-21 2:59 ` andres.ramirez
2014-08-21 6:15 ` Matthew Plant
2014-08-22 9:48 ` Garreau, Alexandre
2014-08-21 20:33 ` Josh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFn2JfmHQRf1xi=0ub09Jod2zjw-zUG6mEQ20XmAsk1=dUGGLA@mail.gmail.com' \
--to=samuel.elborai@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=tumashu@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.