[dev] [vis] [PATCH] Change behaviour of 'cw' and 'cW'

2015-04-03 Thread Matias Linares
from vim's help: cw cW Special case: When the cursor is in a word, "cw" and "cW" do not include the white space after a word, they only change up to the end of the word. This is because Vim interprets "cw" as change-word, and a word does not include the following white space. --- vis.c | 8 +

[dev] [vis] ui separation and mainloop considerations

2015-04-03 Thread Marc André Tanner
I just pushed a fairly invasive change which tries to separate out all the ui related code into a single file: ui-curses.c. The idea is that by implementing the interface of ui.h it should be possible to add a different user interface backend. This should also be useful if somebody finds the time a

Re: [dev] [vis] [PATCH] Change behaviour of 'cw' and 'cW'

2015-04-03 Thread Marc André Tanner
On Fri, Apr 03, 2015 at 05:44:29PM -0300, Matias Linares wrote: > >To prevent errors like these, the various pointers in the Action struct > >should be marked const. > Should I add this changes on the patch? I will do it in a separate patch. -- Marc André Tanner >< http://www.brain-dump.org/ ><

Re: [dev] [vis] [PATCH] Fixed multiline comment regexp.

2015-04-03 Thread Marc André Tanner
On Fri, Apr 03, 2015 at 07:44:22PM +, noname wrote: > Comments like "/***/" with odd number of asterisks are handled like > normal comments now. Previously they were handled like unfinished > comments. Thanks applied! -- Marc André Tanner >< http://www.brain-dump.org/ >< GPG key: CF7D56C0

Re: [dev] [sbase] Anoncoreutils

2015-04-03 Thread Dimitris Papastamos
On Fri, Apr 03, 2015 at 10:43:00AM -0300, Prog Rider wrote: > Maybe you can get some ideas from this. > It was done by a person that's all talk and no action, so don't expect > much. It's old! > http://rechan.eu.org/misc/anoncoreutils-20080617-2.tar.bz2 It is horrible.

Re: [dev] [vis] [PATCH] Change behaviour of 'cw' and 'cW'

2015-04-03 Thread Matias Linares
To prevent errors like these, the various pointers in the Action struct should be marked const. Should I add this changes on the patch? The proper way to fix this is to check in movement(...) whether the action.operator is set to &ops[OP_CHANGE] and if so adjust action.movement accordingly. Wo

Re: [dev] [vis] [PATCH] Fixed multiline comment regexp.

2015-04-03 Thread noname
On Fri, Apr 03, 2015 at 07:21:49PM +0200, Marc André Tanner wrote: > On Thu, Apr 02, 2015 at 02:27:31AM +0300, noname wrote: > > Support for comments without opening "/*" at the beginning of the file > > is removed because people do not normally write comments backwards. > > At the moment vis only

[dev] [vis] [PATCH] Fixed multiline comment regexp.

2015-04-03 Thread noname
Comments like "/***/" with odd number of asterisks are handled like normal comments now. Previously they were handled like unfinished comments. --- config.def.h | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/config.def.h b/config.def.h index ee6d4ae..2a9e258 100644 ---

Re: [dev] [vis] [PATCH] Fixed multiline comment regexp.

2015-04-03 Thread noname
On Fri, Apr 03, 2015 at 07:21:49PM +0200, Marc André Tanner wrote: > On Thu, Apr 02, 2015 at 02:27:31AM +0300, noname wrote: > > Comments like "/***/" with odd number of asterisks are handled like > > normal comments now. Previously they were handled like unfinished > > comments. > > Could you ple

Re: [dev] [vis] [PATCH] Change behaviour of 'cw' and 'cW'

2015-04-03 Thread Marc André Tanner
Thanks for the patch, see the inline comments below for some remarks. > --- > vis.c | 7 +++ > 1 file changed, 7 insertions(+) > > diff --git a/vis.c b/vis.c > index 11cf1af..d18948a 100644 > --- a/vis.c > +++ b/vis.c > @@ -556,6 +556,13 @@ static void op_delete(OperatorContext *c) { > } >

[dev] [vis] [PATCH] Change behaviour of 'cw' and 'cW'

2015-04-03 Thread Matias Linares
from vim's help: cw cW Special case: When the cursor is in a word, "cw" and "cW" do not include the white space after a word, they only change up to the end of the word. This is because Vim interprets "cw" as change-word, and a word does not include the following white space. --- vis.c | 7 +

Re: [dev] [vis] [PATCH] Fixed multiline comment regexp.

2015-04-03 Thread Marc André Tanner
On Thu, Apr 02, 2015 at 02:27:31AM +0300, noname wrote: > Comments like "/***/" with odd number of asterisks are handled like > normal comments now. Previously they were handled like unfinished > comments. Could you please provide a more complete test case? I can't seem to reproduce it here. > Su

Re: [dev] sbase echo.c doesn't respect POSIX

2015-04-03 Thread Louis Santillan
On Fri, Apr 3, 2015 at 4:39 AM, FRIGN wrote: > This is not WhatsApp. ^ | I love you guys!--| :D

Re: [dev] [sbase] Anoncoreutils

2015-04-03 Thread Prog Rider
Its history is similar to sbase: a bunch of guys were displeased with the inefficiency and bloat of current utils and decided to write their own. But those people were all talk and little action, so we only got incomplete stuff. But there might still be some good ideas on the tarball, so I put it o

Re: [dev] [sbase] Anoncoreutils

2015-04-03 Thread Bobby Powers
Hi, Prog Rider wrote: > Maybe you can get some ideas from this. > It was done by a person that's all talk and no action, so don't expect > much. It's old! > http://rechan.eu.org/misc/anoncoreutils-20080617-2.tar.bz2 Are there specifics you find interesting, background or anything else you would l

[dev] [sbase] Anoncoreutils

2015-04-03 Thread Prog Rider
Maybe you can get some ideas from this. It was done by a person that's all talk and no action, so don't expect much. It's old! http://rechan.eu.org/misc/anoncoreutils-20080617-2.tar.bz2

Re: [dev] sbase echo.c is incorrect

2015-04-03 Thread Staven
On Fri, Apr 03, 2015 at 08:17:29AM -0300, Prog Rider wrote: > it doesnt print shit that loons like cmdline arg > This is the best bug report.

Re: [dev] sbase echo.c doesn't respect POSIX

2015-04-03 Thread Prog Rider
I was just trying to get the issues brought up there to you developers. Well, now you know about the thread and can discuss it there. Maybe a new audit? Cheers. On Fri, Apr 3, 2015 at 9:26 AM, Nick wrote: > Quoth Prog Rider: >> What about my other issue? >> echo.c doesnt print shit that loons li

Re: [dev] sbase echo.c doesn't respect POSIX

2015-04-03 Thread Nick
Quoth Prog Rider: > What about my other issue? > echo.c doesnt print shit that loons like cmdline arg I presume "loons" is a typo of "looks". If I understand you correctly, you are wrong: ; ./echo -h -a hello -h -a hello Are you suggesting you thought it would not print '-h -a'? > PS: I don't

Re: [dev] sbase echo.c doesn't respect POSIX

2015-04-03 Thread Prog Rider
What about my other issue? echo.c doesnt print shit that loons like cmdline arg PS: I don't follow E-Mail etiquette because I copy-paste stuff from http://bbs.progrider.org/prog/read/1428010887 Sorry. I hope that's okay for you? Cheers. On Fri, Apr 3, 2015 at 8:39 AM, FRIGN wrote: > On Fri, 3 Apr

Re: [dev] sbase echo.c doesn't respect POSIX

2015-04-03 Thread FRIGN
On Fri, 3 Apr 2015 08:19:19 -0300 Prog Rider wrote: > "The echo utility shall not recognize the "--" argument in the manner > specified by Guideline 10 of XBD Utility Syntax Guidelines; "--" shall > be recognized as a string operand." Update: Upon further discussion with the other guys we decid

Re: [dev] sbase echo.c doesn't respect POSIX

2015-04-03 Thread FRIGN
On Fri, 3 Apr 2015 08:19:19 -0300 Prog Rider wrote: > "The echo utility shall not recognize the "--" argument in the manner > specified by Guideline 10 of XBD Utility Syntax Guidelines; "--" shall > be recognized as a string operand." Hey Prog (?), we read the POSIX spec very closely. The gener

[dev] sbase echo.c doesn't respect POSIX

2015-04-03 Thread Prog Rider
"The echo utility shall not recognize the "--" argument in the manner specified by Guideline 10 of XBD Utility Syntax Guidelines; "--" shall be recognized as a string operand." "Implementations shall not support any options."

[dev] sbase echo.c is incorrect

2015-04-03 Thread Prog Rider
it doesnt print shit that loons like cmdline arg