[dev] morc_menu for i3wm (and others) using dmenu (or others)
A while back, there was some discussion on the Manjaro forums about the desirability of having some form of dmenu that would present applications the way many window managers do, organized by category. So, I wrote it. It's VERY customizable, is not dependent on any window manager, and you can even easily swap out its use of dmenu for some other presenter, such as rofi or (shudder) zenity. project page: https://github.com/Boruch-Baum/morc_menu manjaro forum announcement: https://forum.manjaro.org/index.php?topic=32073.0 The entire 'project' is just a single script file, a single text-formatted configuration file, a man page, and some trivial instructions. I welcome all feedback. Fromm the feedback at Manjaro, it looks like I'll use this project as my first try at packaging for Arch/Manjaro. If anyone wants to package it for some other distro or environment, be in touch so I can link to your work, and get the pleasure of knowing the code is being useful. -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
Re: [dev] structural regular expression support for vis
On Sun, Mar 13, 2016 at 11:07:49AM +, Raphaël Proust wrote: > `ggvG:sam y/\n/i/FOO` only inserts "FOO" at the start of the first > line. It should do it on every line. > Same when using `x/^.*$/` instead of `y/\n/` These should now also work. By the way you do not have to prefix your sam command with `ggvG` because in normal mode it will by default be applied to the whole file. -- Marc André Tanner >< http://www.brain-dump.org/ >< GPG key: 10C93617
Re: [dev] structural regular expression support for vis
First of all, thanks for giving it a try! On Sun, Mar 13, 2016 at 11:07:49AM +, Raphaël Proust wrote: > On 12 March 2016 at 17:44, Marc André Tanner wrote: > > On Fri, Mar 11, 2016 at 08:08:38PM +0100, Marc André Tanner wrote: > >> - There will likely be bugs, memory leaks, crashes, infinite loops etc. > >>YOU are supposed to fix them and submit patches ;) > > When typing `:sam` the editor segfaults. Should be fixed. > > Hence the sam command ,x/pattern/ can be abbreviated to x/pattern > > Because of habit with sam, I started testing with `,x/pattern/` and > got an "Unknown command" message from vis. Without the comma, it > “worked” (i.e., did not print a message). Two things: > > - Are you trying for very high compatibility with vanilla sam? In principle yes, unless there is a good reason to deviate. I tried basing the implementation on the manual page and occasionally on the source if something wasn't clear. Does there exist a more formal standard/description of the command language? > - The message is very confusing. (I first thought the `sam` command > was not recognised by `vis` which lead me to triple chek I had the > correct branch and all. I think the message means that the sam > component of vis thinks I am using `,` as a command and that is > wrong.) Yes this was the case, it should be fixed now. > > - In text entry \t inserts a literal tab character (sam only recognizes > > \n). > > Is it because you plan on having be bound to something like > autocomplete on the command line? It is mainly for convenience. In the past (before the command line was implemented as a regular file) was ignored because lots of vim users would try to auto complete stuff. Also tab expansion also applies to the command line, hence depending on your setting you might not get a literal tab character. This can be worked around with . The same can also be used to enter multi line commands. But to actually execute them one has to mark the selection to execute in visual mode and then press . > There are many bugs related to addressing and such. Please report more examples of the bugs you encountered. > basic examples: > > `ggvG:sam y/\n/i/FOO` only inserts "FOO" at the start of the first > line. It should do it on every line. > Same when using `x/^.*$/` instead of `y/\n/` Haven't really looked into it yet. The problem might be that . also matches new lines. However the "idomatic" way to do this seems to be `x i/FOO` which works. > Something related to vis (but not to the sam component): when typing > `:` the command edition buffer opens. It might be because I'm used > to vim, but I'd rather have that buffer start in normal mode. (Normal > mode is what I expect new buffers to start at.) This might be better indeed. I will see what I like more ... -- Marc André Tanner >< http://www.brain-dump.org/ >< GPG key: 10C93617
Re: [dev] Re: [sbase] [PATCH] sort: Fix -u option
On Sat, Mar 12, 2016 at 03:48:13PM -0800, Michael Forney wrote: > On Sat, Mar 12, 2016 at 11:46:31AM -0800, Michael Forney wrote: > > In eb9bda878736344d1bef06d42e57e96de542a663, a bug was introduced in the > > handling of -1 return values from getline. Since the type of the len > > field in struct line is unsigned, the break condition was never true. > > This caused sort -u to never succeed. > > This should be "sort -c" (here and in subject). > > Please amend before committing. Thanks, applied!
Re: [dev] structural regular expression support for vis
On 12 March 2016 at 17:44, Marc André Tanner wrote: > On Fri, Mar 11, 2016 at 08:08:38PM +0100, Marc André Tanner wrote: >> - There will likely be bugs, memory leaks, crashes, infinite loops etc. >>YOU are supposed to fix them and submit patches ;) When typing `:sam` the editor segfaults. I'll hunt it down and fix it whenever I have a bit of time to spare. > Hence the sam command ,x/pattern/ can be abbreviated to x/pattern Because of habit with sam, I started testing with `,x/pattern/` and got an "Unknown command" message from vis. Without the comma, it “worked” (i.e., did not print a message). Two things: - Are you trying for very high compatibility with vanilla sam? - The message is very confusing. (I first thought the `sam` command was not recognised by `vis` which lead me to triple chek I had the correct branch and all. I think the message means that the sam component of vis thinks I am using `,` as a command and that is wrong.) > - In text entry \t inserts a literal tab character (sam only recognizes \n). Is it because you plan on having be bound to something like autocomplete on the command line? > There are many bugs related to addressing and such. Here are a couple basic examples: `ggvG:sam y/\n/i/FOO` only inserts "FOO" at the start of the first line. It should do it on every line. Same when using `x/^.*$/` instead of `y/\n/` > Something related to vis (but not to the sam component): when typing `:` the command edition buffer opens. It might be because I'm used to vim, but I'd rather have that buffer start in normal mode. (Normal mode is what I expect new buffers to start at.) Cheers, -- __ Raphaël Proust
Re: [dev] structural regular expression support for vis
Not yet, I have it on my agenda for May. On Sat 12-03-2016 18:44 +0100, Marc André Tanner wrote: > On Fri, Mar 11, 2016 at 08:08:38PM +0100, Marc André Tanner wrote: > > > - There will likely be bugs, memory leaks, crashes, infinite loops > > etc. YOU are supposed to fix them and submit patches ;) > > A particularly embarrassing one, preventing the use of multiple > regular expressions in the same command has been fixed. > > I will keep rebasing the branch onto master. > > Did anyone try it out, comments? > -- Jan Christoph Ebersbach I didn’t want some petty, inferior brand of righteousness that comes from keeping a list of rules when I could get the robust kind that comes from trusting Christ - God’s righteousness. Phil 3:9 signature.asc Description: PGP signature
