From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Input methods (Emacs and others), plain X [was: Japanese input in Linux environment]
Date: Thu, 8 Jun 2017 11:12:21 +0200 [thread overview]
Message-ID: <20170608091221.GA7887@tuxteam.de> (raw)
In-Reply-To: <yw.86o9tzr0oh.fsf@zoho.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Jun 07, 2017 at 10:40:46PM +0200, Emanuel Berg wrote:
> > My significant one is a big GNU/Linux fan and
> > uses MATE. Choice is good :)
[...]
> But I think you downgraded the discussion from
> X, Gnome, and KDE. In a book I read that RMS
> (rms) was involved. Gnome was to be for the
> masses and KDE for the techno-druids. This is
> all I remember and I don't remember the name of
> the book either. It must have been good, but
> I lost it somehow.
It's slightly different. The initial main impetus behind
GNOME was that the widget toolkit behind KDE, Qt, wasn't
Free at the time -- something which has changed long, long
time ago.
Then, of course, you had different tribes and what not. I
think that would be a really thrilling case study for an
anthropologist. Perhaps we can learn something from it.
> Still the purpose of the DEs isn't clear to me [...]
You've got to look into one to understand that, and be
it that, like me, you support it for someone else.
> Still we haven't touched upon Wayland, Mir,
> or Unity.
Different things.
But we're far, far off-topic by now. If no one complains
I propose to stop this thread or to take it off-list.
Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlk5FPUACgkQBcgs9XrR2kY80gCeNbIpztJROqKNqTUxgLLgPviN
K4sAnRvPP9GozYaGDBI/O0rD3oDpaOYl
=8NFM
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-06-08 9:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 3:24 Japanese input in Linux environment (fcitx-mozc) Maria Shinoto
2017-06-06 5:37 ` Emanuel Berg
2017-06-06 7:40 ` Lee B
2017-06-06 17:40 ` source liu
2017-06-06 15:04 ` Eli Zaretskii
2017-06-06 23:44 ` Jean-Christophe Helary
2017-06-06 23:54 ` Maria Shinoto
2017-06-07 0:08 ` Jean-Christophe Helary
2017-06-07 0:43 ` Emanuel Berg
2017-06-07 1:35 ` Maria Shinoto
2017-06-07 8:02 ` Héctor Lahoz
2017-06-07 8:13 ` Emanuel Berg
2017-06-07 8:26 ` tomas
2017-06-07 9:24 ` Emanuel Berg
2017-06-07 11:06 ` Input methods (Emacs and others), plain X [was: Japanese input in Linux environment] tomas
2017-06-07 14:51 ` Emanuel Berg
2017-06-07 20:18 ` tomas
2017-06-07 20:40 ` Emanuel Berg
2017-06-08 9:12 ` tomas [this message]
2017-06-08 18:37 ` Emanuel Berg
2017-06-07 15:29 ` Japanese input in Linux environment (fcitx-mozc) Eli Zaretskii
2017-06-09 5:59 ` Maria Shinoto
2017-06-09 7:53 ` Emanuel Berg
2017-06-09 10:58 ` Emanuel Berg
2017-06-09 13:27 ` Bruce V Chiarelli
2017-06-09 19:49 ` ISHIKAWA,chiaki
2017-06-09 19:58 ` ISHIKAWA,chiaki
2017-06-07 5:11 ` Jean-Christophe Helary
2017-06-07 6:26 ` Emanuel Berg
2017-06-07 7:02 ` tomas
2017-06-07 7:17 ` Emanuel Berg
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=20170608091221.GA7887@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@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.
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).