From: Izzie <firstname.lastname@example.org>
Subject: Re: s-tab not working as intended in kde's konsole
Date: Thu, 24 Mar 2011 00:18:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20110324T010632email@example.com> (raw)
Eric S Fraga <e.fraga <at> ucl.ac.uk> writes:
> > Izzie <ml_orgmode.kapush <at> antichef.net> writes:
> > This problem occurs on an aptosid (debian sid 64-bits) laptop with kde when
> > running emacs in konsole with the -nw parameter.
> My experience with console use of emacs is that many key sequences are
> not possible. Some are trapped by whatever terminal emulator is being
> used and others are simply not understood.
I had this problem with gnome-terminal and using zsh but switching to kde fixed
it as it seems konsole does a good job at not getting in the way by dealing
smartly with shortkeys collision, somehow telling when the shortkey should go to
the shell and when it should go to konsole. At least until now, maybe I hadn't
hit the specific key combination that does not work inside konsole yet.
> The trick is to identify which ones are not and provide
> alternative bindings for those commands if you really need them. You
> can, of course, always execute any given command using =M-x command RET=
> (where M-x may have to be invoked by =ESC x=).
> However, one must ask: why use emacs in console mode if you are running
> kde? This does limit what emacs can do.
Remote editing of files through ssh often (but not always) inside screen is the
reason. I know about tramp but haven't had time to look into it yet. I have not
found an equivalent to screen though.
next prev parent reply other threads:[~2011-03-24 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 18:24 s-tab not working as intended in kde's konsole Izzie
2011-03-23 8:56 ` Eric S Fraga
2011-03-24 0:18 ` Izzie [this message]
2011-03-24 9:06 ` Eric S Fraga
2011-03-23 19:03 ` Achim Gratz
2011-03-24 0:38 ` Izzie
2011-03-24 19:31 ` Achim Gratz
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).