headers
Alessandro Piras | 17 Jun 2009 17:44
Picon

I want to contribute!

Hello,
I haven't been active for quite a long time, but I thought I would like to
play with lisp some more and I ran emacs again, of course with vimpulse,
which I and Brad started primarily to play with lisp. I didn't remember how
much the visual selection sucked, in particular:
GVj => the last raw of text is not selected.
So in this moment I'm trying to get a better behavior, and I'm actually
thinking of using an overlay instead of the transient mark mode for visual
highlighting. More news in the next days.
__
Alessandro

2009/4/2 Marius Andersen <rezonatix3 <at> yahoo.no>

>
> > Fra: Stephen Bach <sjbach <at> sjbach.com>
> > Emne: Re: [implementations-list] I want to contribute!
> > Til: "Marius Andersen" <rezonatix3 <at> yahoo.no>
> > Kopi: implementations-list <at> lists.ourproject.org
> >
> > > Currently, I've added an entry to the cond form beginning at line
> > > 1300 in viper-cmd.el (where `viper-prefix-arg-com' is defined), to
> > > associate some simple behavior to `di' (whose cons cell would be
> > > '(?i . ?d)).
> >
> > Hi Marius, good work! How about putting the patch (plus writeup) on
> > the Vimpulse discussion page? It should be hosted somewhere.
>
> I've posted it at http://www.emacswiki.org/emacs/vimpulse . It's
> rather ugly, to be honest, but at least it's a start. :)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Alessandro Piras | 17 Jun 2009 18:04
Picon

I want to contribute!

by the way, I noticed there's a questions in the code comment about an
ugly hack on the parens matching. The question is "what is this code
_trying_ to do?".
let's use an example to explain it:

asdf(jkl)qwer

when the rectangular cursor is on the "(" character, emacs highlights
the matching ")" character. That's fine and it's the same as vim does.
when the cursor is on the ")" instead, emacs does nothing. Emacs need
the cursor to be _after_ the closing paren to match it. So the hack
was, if we are on a closing paren, go forward one character, let emacs
highlight the stuff, go backwards 1 character.

I read it broke other things, so the hack definately sucks.
Does someone have any idea on how to deal with that stuff?

2009/6/17 Alessandro Piras <laynor <at> gmail.com>
>
> Hello,
> I haven't been active for quite a long time, but I thought I would like to play with lisp some more and I ran
emacs again, of course with vimpulse, which I and Brad started primarily to play with lisp. I didn't
remember how much the visual selection sucked, in particular:
> GVj => the last raw of text is not selected.
> So in this moment I'm trying to get a better behavior, and I'm actually thinking of using an overlay instead
of the transient mark mode for visual highlighting. More news in the next days.
> __
> Alessandro
>
> 2009/4/2 Marius Andersen <rezonatix3 <at> yahoo.no>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alessandro Piras | 18 Jun 2009 01:52
Picon

Vimpulse update

Little update to VImpulse.
I'm happy to announce we have a visual mode that (almost) doesn't suck.

   1. works like vim in normal visual mode: the character under the cursor
   when you hit "v" is always selected, and so is the character under the
   cursor when you move.
   2. works like vim in linewise mode: the line you're on is selected, the
   cursor movement is not restricted to the beginning of the line.

As a consequence "0v$" now selects the whole line, not just the characters
up to the second last in the line, and "ggVG" selects everything, not the
text up to the second last line.
In other words, it doesn't suck.
I'm going to upload the stuff on emacs wiki when I discover how to.
There are 2 things that still bother me (i guess more than 2, but only those
come to mind now):
A) the parens matching highlight sucks big time. example:
             if (giancane(cancane(giangiovanni(x), gioacchino(y)),
gianny(x)))
I'd like to hit $ and see if the parens match (in normal mode). But stupid
emacs higlights instead the second last paren. going forward one chare _is
not_ an option, as I would have to hit some stupid arrow key because viper
constrains the movement (and vim too).
So this is the next thing I'm going to look at.

B) Before talking about the annoyance, I must say thanks to the visual block
mode developers, from what I read in the comments, cppjavaperl and Frank
Fisher maybe.
It works great, and it's very usable as is. But it suffers of the same
suckage of the old visual mode:the cursor must be placed 1 column forward of
(Continue reading)

Permalink | Reply | 1 comment |
headers
Alessandro Piras | 19 Jun 2009 05:10
Picon

Re: Vimpulse update

Uploaded the changes.
they are mostly resumed in the history in the .el file.
And.. yeah, we can match parens happily in normal mode now.
__
Alessandro

2009/6/17 Alessandro Piras <laynor <at> gmail.com>:
> Little update to VImpulse.
> I'm happy to announce we have a visual mode that (almost) doesn't suck.
>
> works like vim in normal visual mode: the character under the cursor when
> you hit "v" is always selected, and so is the character under the cursor
> when you move.
> works like vim in linewise mode: the line you're on is selected, the cursor
> movement is not restricted to the beginning of the line.
>
> As a consequence "0v$" now selects the whole line, not just the characters
> up to the second last in the line, and "ggVG" selects everything, not the
> text up to the second last line.
> In other words, it doesn't suck.
> I'm going to upload the stuff on emacs wiki when I discover how to.
> There are 2 things that still bother me (i guess more than 2, but only those
> come to mind now):
> A) the parens matching highlight sucks big time. example:
> ???????????? if (giancane(cancane(giangiovanni(x), gioacchino(y)),
> gianny(x)))
> I'd like to hit $ and see if the parens match (in normal mode). But stupid
> emacs higlights instead the second last paren. going forward one chare _is
> not_ an option, as I would have to hit some stupid arrow key because viper
> constrains the movement (and vim too).
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jason Spiro | 19 Jun 2009 12:07
Picon

Alessandro Piras is the new Vimpulse maintainer

Alessandro Piras, one of the original Vimpulse authors, contacted me
on Gtalk and volunteered to be the new Vimpulse maintainer.
Alessandro, thank you for volunteering.  I hereby appoint you as the
new maintainer.

I think all patches should still go to this list, though Alessandro
gets the final decision on whether that should be so or not.

May I retain my commit rights -- in other words, may I still upload
more changes directly without asking you for permission to upload
them?

Thanks,
--

-- 
Jason Spiro: software/web developer, packager, trainer, IT consultant.
I support Linux, UNIX, Windows, and more. Contact me to discuss your needs.
+1 (416) 992-3445 / www.jspiro.com
Permalink | Reply | 1 comment |
headers
Alessandro Piras | 19 Jun 2009 13:44
Picon

Alessandro Piras is the new Vimpulse maintainer

Yes :)

2009/6/19 Jason Spiro <jasonspiro3 <at> gmail.com>:
> Alessandro Piras, one of the original Vimpulse authors, contacted me
> on Gtalk and volunteered to be the new Vimpulse maintainer.
> Alessandro, thank you for volunteering. ?I hereby appoint you as the
> new maintainer.
>
> I think all patches should still go to this list, though Alessandro
> gets the final decision on whether that should be so or not.
>
> May I retain my commit rights -- in other words, may I still upload
> more changes directly without asking you for permission to upload
> them?
>
> Thanks,
> --
> Jason Spiro: software/web developer, packager, trainer, IT consultant.
> I support Linux, UNIX, Windows, and more. Contact me to discuss your needs.
> +1 (416) 992-3445 / www.jspiro.com
>
> _______________________________________________
> implementations-list mailing list
> implementations-list <at> lists.ourproject.org
> https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
>
Permalink | Reply | 0 comments |
headers
Jason Spiro | 20 Jun 2009 04:59
Picon

http://my-trac.assembla.com/vimpulse

Hi Alessandro,

I had some old unapplied vimpulse patches in my inbox.  Some are still
relevant.  I have started to upload those to
http://my-trac.assembla.com/vimpulse/report/1 -- now I invited you to
Assembla.com so that you can create an Assembla account which will
have read/write access to Trac.  Once I create the account, please
email me privately to remind me to make your Assembla account a
project admin.

Cheers,
Jason

--

-- 
Jason Spiro: software/web developer, packager, trainer, IT consultant.
I support Linux, UNIX, Windows, and more. Contact me to discuss your needs.
+1 (416) 992-3445 / www.jspiro.com
Permalink | Reply | 0 comments |
headers
Marius Andersen | 21 Jun 2009 01:19
Picon
Favicon

I want to contribute!


> Fra: Alessandro Piras <laynor <at> gmail.com>
> Emne: Re: [implementations-list] I want to contribute!
> Til: "Vi/Vim implementations list" <implementations-list <at> lists.ourproject.org>
> Dato: Onsdag 17. juni 2009 15.15
>
> I  didn't remember how  much the visual selection sucked, in particular:
> GVj => the last raw of text is not selected.

For block (rectangular) selection, there's a nice mode included with Cua-mode
(http://www.emacswiki.org/CuaMode). It's probably overlooked by many because Cua-mode's primary
function is to overwrite the standard Emacs keys and use `C-v', `C-c', and `C-x' to paste, copy, and cut,
but this can be avoided by loading the mode as such:

    (cua-mode t)
    (setq cua-enable-cua-keys nil)

Then, to enter block selection mode, hit `C-RET'.

What do you think? Is it better?

      _________________________________________________________
Alt i ett. F? Yahoo! Mail med adressekartotek, kalender og
notisblokk. http://no.mail.yahoo.com
Permalink | Reply | 1 comment |
headers
Alessandro Piras | 21 Jun 2009 05:05
Picon

I want to contribute!

about the current rectangular selection, its main problem is that the
stays on the right of the rightmost selected column.
xxxxx
xxxxx
xxxxx
xxxxxO
where the "x"s indicate the selection, and O indicate the cursor. is
it the same in cua mode?
Also, did you try the latest version of vimpulse? I think it's quite
better now :)
2009/6/20 Marius Andersen <rezonatix3 <at> yahoo.no>:
>
>> Fra: Alessandro Piras <laynor <at> gmail.com>
>> Emne: Re: [implementations-list] I want to contribute!
>> Til: "Vi/Vim implementations list" <implementations-list <at> lists.ourproject.org>
>> Dato: Onsdag 17. juni 2009 15.15
>>
>> I ?didn't remember how ?much the visual selection sucked, in particular:
>> GVj => the last raw of text is not selected.
>
> For block (rectangular) selection, there's a nice mode included with Cua-mode
(http://www.emacswiki.org/CuaMode). It's probably overlooked by many because Cua-mode's primary
function is to overwrite the standard Emacs keys and use `C-v', `C-c', and `C-x' to paste, copy, and cut,
but this can be avoided by loading the mode as such:
>
> ? ?(cua-mode t)
> ? ?(setq cua-enable-cua-keys nil)
>
> Then, to enter block selection mode, hit `C-RET'.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jason Spiro | 21 Jun 2009 09:43
Picon

Alessandro, I think we should get people to agree to assign copyright. Do you?

Hi Alessandro,

The FSF requires that all contributors sign a form agreeing to assign
their copyright to the FSF before the code can get into Emacs.  The
FSF copyright clerk, Mr. Robertson, said that any code contribution 15
lines or more might be copyright-significant.  In the thread I just
forwarded to the list, you can see that he said that.

I think we should get contributors to agree that they will send a
copyright assignment form to the FSF when, hopefully, Vimpulse will
get into Emacs.  Otherwise, if you ask a contributor to assign
copyright and they don't agree, it could be a big headache.  I assume
you would have to delete the code they contributed plus all code that
requires the deleted code.

I propose this.

1.  I edit vimpulse.el saying how to submit patches:

    a)  attach a patch to Trac
    b)  mention that you are willing to assign copyright to the GNU
Project if we ask you to later

2.  If someone submits a patch 15 lines or more and forgot to do 1b),
you ask them, and if they don't agree, you ignore the patch.

You are maintainer, so this is only a suggestion to you.

What do you think?
(Continue reading)

Permalink | Reply | 4 comments |

Gmane