From: "Davis Herring" <herring@lanl.gov>
To: "Lennart Borgman" <lennart.borgman@gmail.com>
Cc: Chong Yidong <cyd@stupidchicken.com>,
ferkiwi+a@gmail.com, joakim@verona.se, emacs-devel@gnu.org
Subject: Re: Why Emacs should have a good web-browser
Date: Wed, 8 Jul 2009 16:05:50 -0700 (PDT) [thread overview]
Message-ID: <44436.130.55.118.19.1247094350.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <e01d8a50907081559p1315cffpf41ceb8f7d928231@mail.gmail.com>
>> On a technical note, I think it makes more sense to associate embedded
>> applications with Emacs windows, rather than buffers as you're
>> apparently trying to do. Â Otherwise, we run into the problem of
>> handling
>> the situation where the same buffer is displayed in more than one
>> window. Â Basically, we should have a way to say "the contents of this
>> window are handled by an embedded program, rather than by Emacs".
>> Â WDYT?
>
> You perhaps still need some buffer elements otherwise the embedded
> application would go away when you closed a window. That could maybe
> be ok, but it is not the way use to behave in Emacs.
>
> Other than that I think it is a good suggestion.
I would say that there should be an "embed object" (sort of like a process
object), and you can do
(set-window-embed window embed)
which fails if EMBED is already associated with some other window. You
would of course have `window-embed' and `embed-window' which would tell
you that association, so that you could do (set-window-embed (embed-window
embed) nil) to detach it and move it around.
(One could also write it as `set-embed-window', which might make the
single-valuedness of the "embed's window" property clearer. But I think
it's important to consider it a property of the window because it
overrides everything else that window could ever do.)
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2009-07-08 23:05 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 20:11 Why Emacs should have a good web-browser Fernando
2009-07-08 20:54 ` Chong Yidong
2009-07-08 21:55 ` joakim
2009-07-08 22:42 ` Lennart Borgman
2009-08-13 22:54 ` Daniel Colascione
2009-07-08 22:55 ` Chong Yidong
2009-07-08 22:59 ` Lennart Borgman
2009-07-08 23:05 ` Davis Herring [this message]
2009-07-09 0:05 ` joakim
2009-07-09 12:36 ` Jason Rumney
2009-07-09 14:25 ` joakim
2009-07-09 16:01 ` Chong Yidong
2009-07-09 17:39 ` joakim
2009-07-09 22:19 ` Richard Stallman
2009-07-08 20:58 ` Richard Riley
2009-07-09 21:12 ` Paul R
2009-07-11 20:24 ` Stefan Monnier
2009-07-12 11:01 ` Robert D. Crawford
2009-07-13 7:18 ` Ken Raeburn
2009-07-17 15:59 ` Paul R
2009-07-18 1:29 ` Miles Bader
2009-07-21 9:18 ` Paul R
2009-07-21 15:52 ` Stefan Monnier
2009-07-21 16:31 ` Miles Bader
2009-07-21 17:25 ` Thomas Lord
2009-07-22 9:23 ` Paul R
2009-07-21 16:52 ` David Reitter
2009-07-21 20:34 ` Chong Yidong
2009-07-21 17:13 ` Thomas Lord
2009-07-21 18:21 ` Adam Wołk
2009-07-21 19:01 ` Lennart Borgman
2009-07-21 19:26 ` Adam Wołk
2009-07-21 19:33 ` Lennart Borgman
2009-07-21 19:47 ` Adam Wołk
2009-07-21 20:02 ` Robert D. Crawford
2009-07-21 20:08 ` Lennart Borgman
2009-07-21 20:37 ` Robert D. Crawford
2009-07-21 20:24 ` Adam Wołk
2009-07-21 21:27 ` Robert D. Crawford
2009-07-21 21:36 ` T.V. Raman
2009-07-21 22:14 ` Robert D. Crawford
2009-07-21 21:48 ` Adam Wołk
2009-07-21 22:24 ` Robert D. Crawford
2009-07-22 10:33 ` Tassilo Horn
2009-07-22 9:12 ` Paul R
2009-07-22 14:47 ` Stefan Monnier
[not found] ` <fxezoucvx5x8i57cbqUYAxe124vaj_firegpg@mail.gmail.com>
2009-07-21 22:09 ` Stephen Eilert
2009-07-21 23:05 ` Chong Yidong
2009-07-22 17:40 ` Stephen Eilert
2009-07-22 18:07 ` Chong Yidong
2009-08-30 18:22 ` joakim
2009-09-02 9:58 ` martin rudalics
2009-09-02 12:00 ` joakim
2009-09-12 19:03 ` Deniz Dogan
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=44436.130.55.118.19.1247094350.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=ferkiwi+a@gmail.com \
--cc=joakim@verona.se \
--cc=lennart.borgman@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 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).