emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Spiers <orgmode@adamspiers.org>
To: emacs-orgmode@gnu.org
Subject: Re: hotkeys for org in gnome
Date: Mon, 24 Dec 2007 12:32:58 +0000	[thread overview]
Message-ID: <20071224123258.GC5797@atlantic.linksys.moosehall> (raw)
In-Reply-To: <f46c52560712232005t965c566h2fff80b96eb13ce0@mail.gmail.com>

Rustom Mody (rustompmody@gmail.com) wrote:
> On Dec 24, 2007 6:32 AM, Adam Spiers <orgmode@adamspiers.org> wrote:
> > On Sat, Dec 22, 2007 at 11:30:52PM +0530, Rustom Mody wrote:
> > > If anyone finds a way of streamlining this please post it!
> >
> > If it's the -c you don't like, you can always dump the commands in a
> > script.  That's nice because it gives you more breathing space to do
> > things like error checking on the exit code of the wmctrl.
> >
> What I dont like is having to use a shell call for some functionality that
> is almost certainly available under elisp.

Why not?  The operation you're talking about (find an emacs, and
ensure it is visible and focused) is more related to the window
manager and X11 environment, so to me it makes much more sense to use
wmctrl than look for some elisp.  Plus, wmctrl is easy and already
works, so why look for an alternative?  I certainly wouldn't class
this solution as an ugly hack; the only slightly ugly thing is
embedding sh -c somewhere, but as I already pointed out, that is
easily surmountable.

      reply	other threads:[~2007-12-24 12:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-15  4:34 hotkeys for org in gnome Rustom Mody
2007-12-16 11:33 ` Adam Spiers
2007-12-16 16:56   ` Rustom Mody
2007-12-17 15:19     ` Adam Spiers
2007-12-17  6:27 ` Dmitri Minaev
2007-12-17 15:20   ` Adam Spiers
2007-12-17 15:41     ` Eric Schulte
2007-12-22 15:52       ` Bastien
2007-12-22 18:00         ` Rustom Mody
2007-12-24  1:02           ` Adam Spiers
2007-12-24  4:05             ` Rustom Mody
2007-12-24 12:32               ` Adam Spiers [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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071224123258.GC5797@atlantic.linksys.moosehall \
    --to=orgmode@adamspiers.org \
    --cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).