From: Userx Xbw <use...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: dwm using just the F keys for keyboard shortcuts
Date: Mon, 27 Jul 2015 06:56:08 -0700 (PDT) [thread overview]
Message-ID: <4c1df5bf-d772-406a-8e06-10658a0244ce@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 776 bytes --]
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 }},
[-- Attachment #1.2: Type: text/html, Size: 1009 bytes --]
next reply other threads:[~2015-07-27 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 13:56 Userx Xbw [this message]
2015-07-27 14:53 ` Userx Xbw
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=4c1df5bf-d772-406a-8e06-10658a0244ce@googlegroups.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).