I just joined this list. Are there downloadable archives somewhere
(ideally in mbox format) for offline browsing?
Kartik
http://akkartik.name/about
Hello,
On Fri, Sep 19, 2014 at 03:13:28PM +0100, Raphaël Proust wrote:
> On Fri, Sep 19, 2014 at 2:22 PM, Maxime Coste wrote:
> > […]
> > That was one of the motivations for swapping selection and operation order
> > in
> > Kakoune (haters gonna hate...), by decoupling selections from the operat
On Fri, Sep 19, 2014 at 2:22 PM, Maxime Coste wrote:
> […]
> That was one of the motivations for swapping selection and operation order in
> Kakoune (haters gonna hate...), by decoupling selections from the operator,
> you
> can express arbitrarily complex selection operations, you have a (rather
Hello
On Fri, Sep 19, 2014 at 02:45:37PM +0200, Hugues Evrard wrote:
> === TL;DR ===
> - editing command could use abstractions that are independent from the
>actual source code syntax
> - e.g., say "comment this line" rather than "add at the
>beginning of the line"
> - pro: offer unif
On Fri, Sep 19, 2014 at 1:45 PM, Hugues Evrard wrote:
> […]
> However, such abstractions require the editor to know the structure of
> language being edited. If this means having a parser for each language
> under edition, then I think it's better to not have such abstractions.
> Still, the inform
> Let me give an example:
> - we want to comment a block of code
> - we edit C-like code, i.e.:
>- let's say a block of code is defined by text between the next "{"
> and its matching "}"
>- comment means add "//" at the beginning of the line
>
> To realize this on "level 2" commands
Hi all,
On 09/17/14 22:12, ale rimoldi wrote:
>
>> Could some vim expert on the list tell me whether it is possible to
>> indent the next n lines by m levels in vim?
>
> the simplest one already works in vis. indent n lines (or better a
> "{" inner area) and repeat the action with dots (eventually
