unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Input methods (Emacs and others), plain X [was: Japanese input in Linux environment]
Date: Wed, 7 Jun 2017 13:06:20 +0200	[thread overview]
Message-ID: <20170607110620.GA24669@tuxteam.de> (raw)
In-Reply-To: <yw.86wp8oqhes.fsf@zoho.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Jun 07, 2017 at 11:24:43AM +0200, Emanuel Berg wrote:

[changing subject, since only peripherally on-topic to thread]

> "plain" X, is that xterm and xpdf and the "x-"
> suite of applications, and starting X manually
> or semi-manually with xinit or startx and then
> configuring the .xinitrc and .Xresources,
> setting up keys with xbindkeys and so on?

Nearly. Xdm started at boot, session via window manager
(Fvwm). Pretty classic. Reached that point after a long
detour through Gnome and a short stay in XFCE.

> If so, I do that as well. It is possible people
> don't do that a lot.

That's my experience, yes.

> I suppose (?) I have Gnome components somewhere
> up and running as the only thing I did to get
> it inhibited was disable the login manager and
> instead launch what I want in X from .xinitrc.

That's the main difference between our setups, I think.

Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEUEARECAAYFAlk33iwACgkQBcgs9XrR2kYQBgCXfbaLHvTmae/Bf4NJP4QPKx0Z
XwCfReFt3252r+jK5vmSStCuBsAmiXE=
=aTbA
-----END PGP SIGNATURE-----



  reply	other threads:[~2017-06-07 11:06 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                   ` tomas [this message]
2017-06-07 14:51                     ` Input methods (Emacs and others), plain X [was: Japanese input in Linux environment] 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
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=20170607110620.GA24669@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).