Re: [dev] [dmenu] Keyboard Bindings
Hey, On 20 November 2011 14:29, Bastien Dejean wrote: > Why aren't all the available keyboard bindings documented in the manual? A lot of them are just standard line editing controls. I don't see any worth in explaining for the umpteenth time what C-h and C-w do... > I don't see any word movement bindings. There aren't any (aside from C-w). I'm considering adding some, but I've not got round to looking at that yet. > I discovered, by accident, that the following input 'foo bar' is > interpreted as the following regex: '.*foo.*bar.*', that's very nice but > I'm not sure that it is mentioned in the manual. That's a new feature which isn't present in any previous release. The manpage alludes to it by saying "... matching the tokens in the input", but clearly it would be nice to be explicit. This will be done by our next release, which we plan to be at Christmas (alongside dwm). Proposed changes are always welcome. ;) Thanks, cls
Re: [dev] [dmenu] Keyboard Bindings
+- Bastien Dejean ---+ > I discovered, by accident, that the following input 'foo bar' is > interpreted as the following regex: '.*foo.*bar.*', that's very nice but if this is true, i use v4.3.1 without this, i would say that this is not nice because of the very same reason you used the word accident. i think we all expect dmenu to match patterns as grep (?) > I'm not sure that it is mentioned in the manual.
Re: [dev] [dmenu] Keyboard Bindings
On Sun, 20 Nov 2011 14:43:59 +0100 Yoshi Rokuko wrote: > i think we all expect dmenu to match patterns as grep (?) nope.
Re: [dev] [dmenu] Keyboard Bindings
On 20 November 2011 14:43, Yoshi Rokuko wrote: > if this is true, i use v4.3.1 without this, i would say that this > is not nice because of the very same reason you used the word accident. I would invite you to try it first. We use unstable sorting just like before, which means "ba an" will match "banana" before "anbana", and it is very rare that you intend to actually match whitespace. (I've never needed to, ever.) With dmenu_run, for instance, do you have programs with spaces in the name? No. Do you have URLs with spaces in? It's unlikely. So being able to avoid typing "gnome-vo" to get up "gnome-volume-control" (yeah, I have to use Gnome on one machine), instead you type "g vo". Want to match a URL on a given site? Instead of typing "hg.suckless.org/tabbed" (or typing "hg" and scrolling down 30 items), type "hg t". You have no idea how much more efficient this makes you. Give me a situation where literal whitespace is more useful than token matching... cls
Re: [dev] [dmenu] Keyboard Bindings
+ Connor Lane Smith ---+ > I would invite you to try it first. We use unstable sorting just like > before, which means "ba an" will match "banana" before "anbana", and > it is very rare that you intend to actually match whitespace. (I've > never needed to, ever.) With dmenu_run, for instance, do you have > programs with spaces in the name? No. Do you have URLs with spaces in? > It's unlikely. i agree on url and program names, but i use whitespace match with grep on plain text. > So being able to avoid typing "gnome-vo" to get up > "gnome-volume-control" (yeah, I have to use Gnome on one machine), > instead you type "g vo". Want to match a URL on a given site? Instead > of typing "hg.suckless.org/tabbed" (or typing "hg" and scrolling down > 30 items), type "hg t". You have no idea how much more efficient this > makes you. > > Give me a situation where literal whitespace is more useful than token > matching... i use dmenu only on url and program names, i used it for file names too, but my files do not have whitespaces, and i agree that typing 'hg ta' is much faster then 'hg.*ta', but i think one should not touch REGEXP(7) in a single program that is part of a toolkit ... you know what i mean. i am not talking about legacy support or change in general, i would love it if dmenu would support REGEXP(7) patterns. best regards, yoshi
Re: [dev] [dmenu] Keyboard Bindings
On Sun, 20 Nov 2011 19:28:14 -, Yoshi Rokuko wrote: i use dmenu only on url and program names, i used it for file names too, but my files do not have whitespaces, and i agree that typing 'hg ta' is much faster then 'hg.*ta', but i think one should not touch REGEXP(7) in a single program that is part of a toolkit ... you know what i mean. i am not talking about legacy support or change in general, i would love it if dmenu would support REGEXP(7) patterns. To me, regexp does not seem like a good expression language for matching IRIs and pathnames. First and foremost, pathnames are easily tokenized, rendering the power of regular expressions unnecessary. Secondly, pathnames often contain dots - and IRIs even more so. Reserving the dot is not an option IMHO. Would you ever use character sets or classes in dmenu? I most certainly won't. -- -,Bjartur
Re: [dev] [dmenu] Keyboard Bindings
On Sun, 20 Nov 2011 20:28:14 +0100 Yoshi Rokuko wrote: > i use dmenu only on url and program names, i used it for file names too, > but my files do not have whitespaces, and i agree that typing 'hg ta' > is much faster then 'hg.*ta', but i think one should not touch REGEXP(7) > in a single program that is part of a toolkit ... you know what i mean. > > i am not talking about legacy support or change in general, i would > love it if dmenu would support REGEXP(7) patterns. > > best regards, yoshi > I don't understand... Are you saying "I agree the token matching works fine and is the fastest, but I still want you to implement an inferior and more complicated approach (regexes)" ? Dieter
Re: [dev] [dmenu] Keyboard Bindings
On 20/11/2011, Bjartur Thorlacius wrote: > pathnames often contain dots - and IRIs even more so. Reserving the dot is > not an option IMHO. > > Would you ever use character sets or classes in dmenu? I most certainly > won't. Indeed, I think the nature of dmenu is very different from grep, since it is very interactive. grep is a command, whereas dmenu is an interface, and I think they need to be treated differently. A while back I did write a dmenu patch which uses regcomp(3), which I could rustle together for you if you'd like. It won't ever be in mainline, though. cls
Re: [dev] [dmenu] Keyboard Bindings
+--- Dieter Plaetinck ---+ > I don't understand... Are you saying "I agree the > token matching works fine and is the fastest, but I > still want you to implement an inferior and more > complicated approach (regexes)" ? i don't want you to implement regexp, i'm quite happy with v4.3.1, i will even upgrade in the future and if you have some token matching implemented i will get used to it - have no fear. however for me regexp is not inferior to your token matching, it is more versatile and people are used to it - it is common. i'm just sceptical about this 'yet another matching scheme' ...
Re: [dev] [dmenu] Keyboard Bindings
+--- Connor Lane Smith ---+ > On 20/11/2011, Bjartur Thorlacius wrote: > > pathnames often contain dots - and IRIs even more so. > > Reserving the dot is not an option IMHO. > > > > Would you ever use character sets or classes in dmenu? > > I most certainly won't. > > Indeed, I think the nature of dmenu is very different from grep, > since it is very interactive. grep is a command, whereas dmenu > is an interface, and I think they need to be treated differently. it seems that i cannot communicate my point - why are vi-styled-key- binding-styled-interfaces so popular? i'm not sure i like your distinction between 'command' and 'interface' by the way, although it makes me think about it. regards, yoshi
Re: [dev] [dmenu] Keyboard Bindings
On Mon, 21 Nov 2011 09:59:49 +0100 Yoshi Rokuko wrote: > +--- Dieter Plaetinck ---+ > > I don't understand... Are you saying "I agree the > > token matching works fine and is the fastest, but I > > still want you to implement an inferior and more > > complicated approach (regexes)" ? > > i don't want you to implement regexp, i'm quite happy > with v4.3.1, i will even upgrade in the future and if > you have some token matching implemented i will get > used to it - have no fear. > > however for me regexp is not inferior to your token > matching, it is more versatile and people are used to > it - it is common. i'm just sceptical about this 'yet > another matching scheme' ... > FWIW, re "yet another": token matching is also implemented in xmms, firefox (awesomebar), chromium/chrome and with uzbl/luakit(/surf?) by using dmenu and AFAIK users love it. probably even some more cases i'm not aware of.. Dieter
Re: [dev] [dmenu] Keyboard Bindings
On 21 November 2011 09:15, Yoshi Rokuko wrote: > it seems that i cannot communicate my point - why are vi-styled-key- > binding-styled-interfaces so popular? It's not vi-style, it's Unix. If you come from a Windows background, you'll be used to Ctrl+Backspace to delete a word, or Shift+Home, Backspace to delete a line. Unix has C-W and C-U, it's just muscle memory. Rob.
Re: [dev] [dmenu] Keyboard Bindings
The first applications I remember using this kind of pattern matching were winamp and web search engines.
Re: [dev] [dmenu] Keyboard Bindings
+-- Rob ---+ > On 21 November 2011 09:15, Yoshi Rokuko wrote: > > it seems that i cannot communicate my point - why are vi-styled-key- > > binding-styled-interfaces so popular? > > It's not vi-style, it's Unix. If you come from a Windows background, > you'll be used to Ctrl+Backspace to delete a word, or Shift+Home, > Backspace to delete a line. Unix has C-W and C-U, it's just muscle > memory. i really like ^U, ^W, ^H, ^A, ^E unfortunatly these are not vim default, what i meant was stuff like vimperator, cmus and so on. but like you said its muscle memory.
Re: [dev] [dmenu] Keyboard Bindings
[2011-11-21 10:12] Rob > On 21 November 2011 09:15, Yoshi Rokuko wrote: > > it seems that i cannot communicate my point - why are vi-styled-key- > > binding-styled-interfaces so popular? > > It's not vi-style, it's Unix. If you come from a Windows background, you'll > be used to Ctrl+Backspace to delete a word, or Shift+Home, Backspace > to delete a line. Unix has C-W and C-U, it's just muscle memory. Uriel created a page once: http://unix-kb.cat-v.org/ meillo
