Dmytro Kolomoiets

Results 51 comments of Dmytro Kolomoiets

OK, I was too hasty, my bad. Actually, there is still the case, which comments can't solve gracefully: ```cmake find_program(mkrc_exe NAMES elf-resource-make) # function(make_resource_from_each) ... endfunction() # function(make_resource nm src)...

> Insert n spaces before a statement which opens scope > In other words, same rule for if() and foreach(), etc.? If they are inside function/macro -- keep no more...

I think the issue would be elegantly solved if there existed a widely accepted **standard proprietary license**, with maximum possible rights reserved, added to spdx list alongside other FOSS licenses....

I would liked as well such feature as one space addition, as I used this extenively with vim-surround when shell/perl scripting. And now I'm use own awful replacement for this...

I have created [bugreport](https://github.com/neovim/neovim/issues/3688) on neovim issue tracker. Seems like it will be fixed someday. If we are lucky -- until 0.2 milestone.

@wmvanvliet I tried again and again in hope it will work "somehow" in last month. Because it's simply too sweet to part with function's local vars exploration. And I miss...

I'm trying to port selfspy repo to XCB and had stumbled on trying to convert create_context semantic to XCB due to this :) * https://github.com/selfspy/selfspy/blob/master/selfspy/sniff_x.py#L69 Any ideas how to workaround...

Ok, let's share at least my monkey-patches for Record extension. I encourage anyone to send them as proper pull request instead: ```python import xcffib.record as xrec ## HACK: monkey-patched xcffib...

Alternative approach if you use only single PC at a time -- always keep tomb (without key) on some cloudsync. Then do "pass open" on local db, manually open tomb...

@jerabaul29, sorry, I see only cons in your approach. Isn't my approach described above much greater ? :) ```bash pass git init sudo install -m 700 -o "$USER" -g "$USER"...