Stephen Bach | 1 Sep 20:11 2010

[Vimpulse] /-search incremental highlighting is always case insensitive

Hi,

I really like the new isearch-style /-search, but I notice the
highlighting as I'm typing a search term, as well as the first search
selection, are always case insensitive.  So, given this text:

  ASDF
  asDf
  asdf

If viper-case-fold-search is nil and I search for "asdf", all of the
variants of asdf highlight, and after pressing enter the cursor moves to
ASDF, but subsequent presses of "n" will only go to asdf (even though
the other variants stay highlighted as if they are also matched).

As a side-note, it'd be nice if the old viper trick of typing "/" twice
quickly to change case sensitivity still worked -- but since this isn't
a Vim thing, I can understand why we didn't bother keeping it around.

_______________________________________________
implementations-list mailing list
implementations-list <at> lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Vegard Øye | 1 Sep 21:28 2010
Picon

Re: Oh those periods

On 2010-08-30 23:33, Štěpán Němec wrote:

> Apart from a _very_ few exceptions, _everybody_ ended the commit
> summaries with a period. Period. (I still have the old Git tree
> handy in case you don't.)

The old Git tree is misleading, as I used `git commit --amend' to add
the missing periods before pushing. It seemed too petty (and a waste
of people's time) to request a new patch over mere punctuation.

The exceptions you see -- that's me, forgetting to check for
conformance with this arbitrary, impractical and, thankfully,
obsolete rule.

--

-- 
Vegard

_______________________________________________
implementations-list mailing list
implementations-list <at> lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Vegard Øye | 2 Sep 22:19 2010
Picon

Re: [Vimpulse] /-search incremental highlighting is always case insensitive

On 2010-09-01 20:11, Stephen Bach wrote:

> If viper-case-fold-search is nil and I search for "asdf", all of the
> variants of asdf highlight, and after pressing enter the cursor
> moves to ASDF, but subsequent presses of "n" will only go to asdf
> (even though the other variants stay highlighted as if they are also
> matched).

Should be fixed in commit 6327facd, where `viper-case-fold-search' is
made an alias for `case-fold-search'.

> As a side-note, it'd be nice if the old viper trick of typing "/"
> twice quickly to change case sensitivity still worked -- but since
> this isn't a Vim thing, I can understand why we didn't bother
> keeping it around.

Since Vimpulse's search is just isearch in disguise, you can type M-c
at any point to change the case-sensitivity of the search. (See the
docstring of `isearch-forward' for more cool shortcuts.)

--

-- 
Vegard
Štěpán Němec | 9 Sep 17:17 2010
Picon

[OT] Git User's Survey 2010


Hello everybody,

I just thought I bring this up in case anyone wants to contribute: Git
has been organising a survey every year for some time, and now's the
time to take it this year (up to October 15), so please do take the
survey (it's not too long, can be fun and other than contributing a bit
to development of our beloved VCS you might even learn about features
mentioned there you had no idea about ;-)):

http://git.wiki.kernel.org/index.php/GitSurvey2010
Štěpán Němec | 9 Sep 17:21 2010
Picon

Re: [Vimpulse] Arrow keys don't work as motions

Nick Smallbone <nick.smallbone <at> gmail.com> writes:

> Štěpán Němec <stepnem <at> gmail.com> writes:
>> Is the `characterp' -> `integerp' change really necessary? On XEmacs,
>> (integerp ?\C-0) => nil, although the integer <--> character arithmetic
>> (`-', `logand') works the same as in GNU Emacs.
>
> On GNU Emacs it's the other way round: (characterp ?\C-0) => nil, but
> (integerp ?\C-0) => t. What if we changed it to use
> (or (characterp char) (integerp char)) instead?

Sounds good. Any reason not to do that, Vegard?

_______________________________________________
implementations-list mailing list
implementations-list <at> lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Vegard Øye | 10 Sep 12:23 2010
Picon

Re: [Vimpulse] Arrow keys don't work as motions

On 2010-09-09 17:21, Štěpán Němec wrote:

> Nick Smallbone <nick.smallbone <at> gmail.com> writes:
>
>> What if we changed it to use (or (characterp char) (integerp char))
>> instead?
>
> Any reason not to do that, Vegard?

Done in commit e74dd44.

--

-- 
Vegard

_______________________________________________
implementations-list mailing list
implementations-list <at> lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Vegard Øye | 12 Sep 15:11 2010
Picon

[ANN] Vimpulse 0.5

http://www.emacswiki.org/emacs/vimpulse.el

This release changes Vimpulse's dependencies: it now uses undo-tree.el
instead of redo.el. undo-tree.el can be obtained from:

http://www.emacswiki.org/emacs/UndoTree

Just place it somewhere in your `load-path', and Vimpulse will
load it automatically. (You can still use redo.el with XEmacs,
but without the tree functionality of undo-tree.el.)

News:

- [NEW] :undolist or :ul shows the undo history as a tree. This
  uses undo-tree.el, which replaces redo.el for undo/redo.
- [NEW] "/" and "?" use isearch. Matches are highlighted while
  typing; also, isearch shortcuts apply, like "M-c" to toggle
  case-sensitivity. Type "C-h k /" for more details.
- [NEW] Keybinding functions: `vimpulse-global-set-key',
  `vimpulse-local-set-key', `vimpulse-define-key'. State bindings
  can be assigned to both minor and major Emacs modes, which is
  useful for extensions.
- [NEW] Keys: "gi", "g0", "g$", "]P", "]p".
- [NEW] Lower-case marks are buffer-local -- thanks, Štěpán Němec.
- [NEW] If `viper-auto-indent' is t, then "RET" extends the
  comment prefix to the next line (with `comment-indent-new-line'
  from newcomment.el).
- [NEW] "C-w" has its own prefix map, `vimpulse-window-map'.
- [FIX] Replace mode's appearance is more similar to Vim's.
- [FIX] Byte compilation errors.
(Continue reading)

Stephen Bach | 27 Sep 04:33 2010

[Vimpulse] `make big` target

Hi,

There seems to be a problem with the `big` Makefile target - the elisp
produced appears to be unparseable, at least for me.  ("End of file
during parsing" -- and trying to track down paren imbalances is a dog,
so I didn't try very hard to pinpoint the issue.)

_______________________________________________
implementations-list mailing list
implementations-list <at> lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Daimrod | 27 Sep 13:21 2010
Picon

[Vimpulse] substitute bug


Hi,

There is a problem with the substitute command in the case I want to
substitute "something" by "set<space>something".

So, the following command fails when I hit the space key.
    :s/something/set something
The substitute command is simply cancelled.

PS:
I've the same problem than Stephen Bach with the `make big` command,
but I didn't figure out how to reply to his mail because I've signed
up for the list after his mail. 
However, I think the problem is in the file:
"vimpulse-viper-function-redefinitions.el" line 907
(something is wrong with the brackets)

PPS: Sorry if I made any mistake.
Štěpán Němec | 27 Sep 13:41 2010
Picon

Re: [Vimpulse] `make big` target

Stephen Bach <sjbach <at> sjbach.com> writes:

> Hi,
>
> There seems to be a problem with the `big` Makefile target - the elisp
> produced appears to be unparseable, at least for me.  ("End of file
> during parsing" -- and trying to track down paren imbalances is a dog,
> so I didn't try very hard to pinpoint the issue.)

Yeah... 37945c50fd (Remove superfluous Visual code) broke it.
Actually, my guess is that the fix is trivial -- Vegard made a simple
change cramming multiple froms under a single `eval-when-compile', which
the simple `sed' hack used to strip these forms does not grok.

OTOH, we should just definitively remove the big file support.

Vegard, what do you think? (BTW, you should actually use the makefile
test targets to check for breakages before you push changes, you know
;-))

To anybody still using the single-file version, I recommend using the
multiple files. It's also less hassle, actually -- just put the vimpulse
directory into your `load-path' and you're all set.

Štěpán

_______________________________________________
implementations-list mailing list
implementations-list <at> lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
(Continue reading)


Gmane