all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Copley <rcopley@gmail.com>
To: "René Kuligowski" <renekuligowski@alice-dsl.net>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Questions: classical X embedding, vc for Fossil
Date: Thu, 8 Dec 2016 19:58:42 +0000	[thread overview]
Message-ID: <CAPM58oh-Z+fK28xVT5oR0uqS0s8EgXL3TZvOJbZ8rMRv-zGdog@mail.gmail.com> (raw)
In-Reply-To: <58494203.4080406@alice-dsl.net>

On 8 December 2016 at 11:20, René Kuligowski
<renekuligowski@alice-dsl.net> wrote:
> Me again, Forgot one thing:
>
> On 08.12.2016 09:51, René Kuligowski wrote:
>
> (…)
>>
>> concerning the X-embedding: yes, it matters, in a way –– why embed an own
>> DocView pane for DVI/PDF- and image-viewing, but staying there when it would
>> be easy *and* make sense to do the same for the three browsers (w3, w3m,
>> eww) to use the full capabilities of a graphical pane instead of a textual
>> one.  IMHO the GTK3-Webkit-widget-embedding is sort of a short-circuited
>> action without any sense or purpose and should have been replaced with
>> native X pane/widget embedding.
>>
> …for, eg., an AuCTeX/syncTeX preview pane, an embedded xterm as
> fully-capable shell launched by eshell-visual-command, using X-widgets for
> customize, ses, etc.  The possibillities are almost endless.  Think about
> it, it makes sense.

Nope! Acronym salad. I can't make head nor tail of it. :)

> Again, best regards, ;-)



      reply	other threads:[~2016-12-08 19:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03  8:02 Questions: classical X embedding, vc for Fossil René Kuligowski
2016-12-06 22:38 ` Richard Copley
     [not found]   ` <58493B42.9070203@alice-dsl.net>
2016-12-08 11:20     ` René Kuligowski
2016-12-08 19:58       ` Richard Copley [this message]

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=CAPM58oh-Z+fK28xVT5oR0uqS0s8EgXL3TZvOJbZ8rMRv-zGdog@mail.gmail.com \
    --to=rcopley@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=renekuligowski@alice-dsl.net \
    /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.