From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Input methods (Emacs and others), plain X [was: Japanese input in Linux environment]
Date: Thu, 08 Jun 2017 20:37:07 +0200 [thread overview]
Message-ID: <yw.86bmpyfhrg.fsf@zoho.com> (raw)
In-Reply-To: 20170608091221.GA7887@tuxteam.de
> 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.
Cute! That was it. Now I remember. This was
explained it the book as well.
> 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.
>
> [...]
>
> You've got to look into one to understand
> that, and be it that, like me, you support it
> for someone else.
Long before I ever saw Gnome and KDE, I saw
Linux systems (or if it was BSDs or whatever)
that looked like desktop systems. They had the
xclock and tons of small windows scattered over
a high-resolution monitor, and basically every
window had the "x" prefix in the titlebar.
It didn't look as neat and polished as Finder
but not as tasteless as Windows. It was
a higher degree of hacker appeal despite being
a GUI.
Now what exactly is the difference between such
a paleo-graphical Unix system and a system that
has a desktop suite like Gnome or KDE?
Aren't DEs illogical no matter what one
thinks of them?
OS > GFX system > ( terminal emulator )_WM > launch programs from shell
If if you aren't into shell/batch/text-based
computing but like GUIs with a "Start" menu
etc., doesn't that just translate into
OS > GFX system > ( "Start" menu & file browser )_WM > launch programs by mouse-clicking
?
Obviously anyone can call their programs
whatever they want, including gnome-screenshot
and gnome-terminal. In a way, my very reasoning
could be applied to xterm and xpdf as well -
I mean, what's X about them? They are just
applications like any other that are
executable/viewable in X.
It is possible tho that the degree of
modularity and independence to software
development were different back then in that
that you actually had to adapt software at the
end of the line to the underlying X.
It is also possible it is just a phycological
thing to make big systems out of small
components, and try to force the components
into a fold that is common to all.
My "train" goes in the other direction, i.e.
the system is bigger than the component, but
hey, real trains are actually bi-directional as
long as they have two locomotives.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-06-08 18:37 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
2017-06-08 18:37 ` Emanuel Berg [this message]
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=yw.86bmpyfhrg.fsf@zoho.com \
--to=moasen@zoho.com \
--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).