134 reputation
4
bio website guillaume-nargeot.blogspot.co…
location Japan
age 30
visits member for 4 years, 5 months
seen Dec 3 at 11:34
e-mail: killy971@gmail.com
blog: http://guillaume-nargeot.blogspot.com/

Language used:
  • Java
  • Ruby
  • Clojure

Jun
5
comment Make a key behave as a switch or a normal key based on how long it was kept pressed down, using AutoHotKey
I'm going to edit and reformulate my question. It's as simple as: I want to remap a key to being both usable as an "Enter" when pressed and released in less than 500ms, and usable as a switch to create other mappings (ex. WASD arrow keys), to simulate the same behavior as the Fn key of some keyboards
Jun
4
revised Make a key behave as a switch or a normal key based on how long it was kept pressed down, using AutoHotKey
added 138 characters in body
Jun
4
awarded  Editor
Jun
4
revised Make a key behave as a switch or a normal key based on how long it was kept pressed down, using AutoHotKey
added 415 characters in body
Jun
4
asked Make a key behave as a switch or a normal key based on how long it was kept pressed down, using AutoHotKey
Mar
4
comment Why is the grep/-r/--include combination slower than the find/-exec/grep combination?
Interesting, but in my case the fhandler count is almost the same, and actually it's even higher for find (~7%): - count for find: 156389 - count for grep: 145734
Mar
4
awarded  Supporter
Jan
18
comment Why is the grep/-r/--include combination slower than the find/-exec/grep combination?
As I mentioned, the directory tree I'm running these commands on contains a lot of files, likely between 10k and 100k, and there are only 10 files which match the filename pattern, and grep is therefore run only on those 10 files. Moreover, each of these file is very small, and the time spent on grepping them must be only a few ms. This is why I feel that it's the way "grep" visits the directory tree that is inefficient compared to "find". I'm still trying to figure out the meaning of what I see in the output of strace, but I can already tell that grep/incl performs a larger # of ops on files
Jan
18
comment Why is the grep/-r/--include combination slower than the find/-exec/grep combination?
By warming up, I meant that I ran the command multiple times until stabilization of performance. Regarding the files and directories I used, it's a java code base, with xx,xxx files and just 10 to 20 small (< 100kb) xml files, which are the target of my grep command.
Jan
18
awarded  Student
Jan
18
asked Why is the grep/-r/--include combination slower than the find/-exec/grep combination?
Jul
6
awarded  Autobiographer