Void Linux discussion
 help / color / mirror / Atom feed
From: Userx Xbw <use...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: dwm using just the F keys for keyboard shortcuts
Date: Mon, 27 Jul 2015 09:53:44 -0500	[thread overview]
Message-ID: <CA+vT7e5LOU=36mHeqBrvyZAM_hFJ0QGPBouA=4nK9a1eNKkK9g@mail.gmail.com> (raw)
In-Reply-To: <4c1df5bf-d772-406a-8e06-10658a0244ce@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]

solved

add
#include <X11/XF86keysym.h>

and make it XK_F2

in config.h

On Mon, Jul 27, 2015 at 8:56 AM, Userx Xbw <use...@gmail.com> wrote:

> in i3 I can use just an F Key (ie f2) and asign it to a shotcut to start
> an application -- when using the same metholid in dwm it's not working, I
> have yet to find any documentaion on this. what syntex to use for F keys
>
>  this is what i am doing
>
> in i3 config it's as easy as this
>
> bindsym F2  exec --no-startup-id terminology
>
> in DWM wm this is what I used, but it is not accepting the syntex a simple
> F2
>
> static const Rule rules[] = {
>         /* class      instance    title       tags mask     isfloating
> monitor */
>
>         { "terminology", NULL,              0,            True,        -1
> },
>
>
>
> };
>
> ...
>
> static const char *terminologycmd[] = {"terminology", NULL};
>
>
> .......
> { SUPKEY,                       F2,        spawn,         {.v =
> terminologycmd }},
>
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "voidlinux" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/voidlinux/tAZD1t1Dy2k/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> voidlinux+...@googlegroups.com.
> To post to this group, send email to void...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/voidlinux/4c1df5bf-d772-406a-8e06-10658a0244ce%40googlegroups.com
> <https://groups.google.com/d/msgid/voidlinux/4c1df5bf-d772-406a-8e06-10658a0244ce%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

[-- Attachment #2: Type: text/html, Size: 2725 bytes --]

      reply	other threads:[~2015-07-27 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 13:56 Userx Xbw
2015-07-27 14:53 ` Userx Xbw [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

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

  git send-email \
    --in-reply-to='CA+vT7e5LOU=36mHeqBrvyZAM_hFJ0QGPBouA=4nK9a1eNKkK9g@mail.gmail.com' \
    --to="use..."@gmail.com \
    --cc="void..."@googlegroups.com \
    /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 NNTP newsgroup(s).