And we should probably continue that discussion on
https://github.com/mawww/kakoune/issues/541
On Wed, Mar 02, 2016 at 06:32:08PM +, Connor Lane Smith wrote:
> > * support lookaheads and lookbehinds, until I find a clean, alternative way
> >to express 'a double quote that is not preceeded by a pair number of
> >antislash' to match the closers of C strings (as an example of their
On Wed, Mar 02, 2016 at 04:16:02PM +, Connor Lane Smith wrote:
> On 2 March 2016 at 15:45, Maxime Coste wrote:
> > How does sam handles parallel grouping when we get multiple incompatible
> > changes
> > to the same range of text ?
>
> It panics.
>
> In
On Wed, Mar 02, 2016 at 03:17:49PM +0100, Marc André Tanner wrote:
> On Wed, Mar 02, 2016 at 10:40:51AM +0000, Maxime Coste wrote:
> > On Wed, Mar 02, 2016 at 10:14:48AM +, Raphaël Proust wrote:
> > > On 1 March 2016 at 17:12, Marc André Tanner wrote:
> > > >
On Wed, Mar 02, 2016 at 10:14:48AM +, Raphaël Proust wrote:
> On 1 March 2016 at 17:12, Marc André Tanner wrote:
> > I think structural regexp will integrate nicely with multiple selections.
> >
> > […]
>
> Yes! Interactive structural regexp would definitely be a Killer
> Feature™ IMO. I woul
Hello
On Mon, Feb 15, 2016 at 05:34:58PM +0100, Marc André Tanner wrote:
> In general what kind of data structure do you use to keep track of cursors
> when the buffer changes? That is when something is inserted/deleted at a
> cursor location, do you need to update the location of all subsequent
>
On Sat, Feb 13, 2016 at 02:11:28PM +0100, Marc André Tanner wrote:
> On Mon, Jan 18, 2016 at 08:24:14AM +0100, Jan Christoph Ebersbach wrote:
> > - I miss that I can't align multiple cursors in insert mode, i.e. to
> > align all "=" over multiple lines. The editor kakoune supports this
> > nic
On Thu, Nov 20, 2014 at 07:56:29AM +0100, ans...@garbe.us wrote:
> > But regarding the typedefs for structs: C has only a few namespace
> > features, so lets not dismantle the probably most used one, alright?
> > "struct stat" can be something different from "stat()"! I like that
> > namespace thin
Hello,
On Wed, Nov 19, 2014 at 12:19:15PM -0600, Josh Lawrence wrote:
> So for those of you that participate in the suckless community in some
> way: What do you run on your computer, and why?
I use Exherbo, which is similar to Gentoo but more decentralized, (and probably
less user friendly). I
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 dec
mmands
The hard part being finding that expressive set of core commands.
The problem with parsers is that besides being quite slow if data driven, they
are not very good at analysing invalid code, which is the most common state of
code being edited.
Cheers,
Maxime Coste.
On Wed, Sep 17, 2014 at 09:40:44PM +0200, q...@c9x.me wrote:
> On Wed, Sep 17, 2014 at 07:42:47PM +0100, Maxime Coste wrote:
> > > That doesn???t happen that often to justify overloading. Hint: Avoided
> > > complexity in the system *beforehand*.
> >
> >
On Wed, Sep 17, 2014 at 06:29:01AM +0200, Christoph Lohmann wrote:
> On Wed, 17 Sep 2014 06:29:01 +0200 Maxime Coste wrote:
> > On Tue, Sep 16, 2014 at 11:02:40PM +0200, Christoph Lohmann wrote:
> > > This is programming and not your playground. Avoid fancy code.
> >
>
he preprocessor
can be a pain, and the whole compilation model does not scale.
All I'm saying here is, sucky programs can be written in any language,
and I do not like to see Kakoune rejected on the sole ground of its
implementation language.
Cheers,
Maxime Coste.
), and you
> have to use a lot of them in c++. I think the mess is the type
> system of c++.
Oh boy, you don't know much about C++ do you, of course a char* is
implicitely convertible to const char*. On pointer semantics, the
only difference between C and C++ is that void* is not implicitely
convertible to other pointer types (from is ok).
Cheers,
Maxime Coste.
://bartoszmilewski.com/2013/09/19/edward-chands/
That last one is by far the most interesting, Bartos being very familliar with
C++. Note that its not C that is advocated, but haskell...
Cheers,
Maxime Coste.
ly be avoided by changing and restricting the system.
I blame that on .net... More seriously, yep there is a lot of ugly C++ out
there, and OOP nonsense, I've seen my share of extra deep class hierarchies
with virtual methods everywhere. That code might have been written in C++,
but its very far from idiomatic, modern C++. The ioccc tends to show that
C is far from imune from unintelligile code.
Regards,
Maxime Coste.
On Tue, Sep 16, 2014 at 11:20:45PM +0200, Roberto E. Vargas Caballero wrote:
> > Ok, so what exactly is the sum of 3 lines and 2 bytes ? The whole point
> > is to catch at compilation code that is logically invalid, if you have
> > f(ByteCount, LineCount), you cannot call it with a (LineCount, Byte
r of elements).
> Stop this C++ proselytism because the only thing you are going to
> get is becoming a troll. If you like maschoshism is your problem, but
> please don't tell to us.
Can't we have a civilized discussion ?
Cheers,
Maxime Coste.
in practice a dynamic
array provides you with much better performance characteristics.
Cheers,
Maxime Coste.
Hi
On Mon, Sep 15, 2014 at 11:50:52PM +0300, Dimitris Zervas wrote:
> On September 15, 2014 6:41:29 PM EEST, q...@c9x.me wrote:
> >On Mon, Sep 15, 2014 at 02:21:25PM +0100, Maxime Coste wrote:
> >> Hello,
> >> [...]
> >> Maxime Coste.
> >
> >I like
he vi-like user interface, and trying
to improve the implementation without trying to improve the design itself
seems like a waste.
Anyway, best of luck on your project, writing a code editor is a very
rewarding experience.
Cheers,
Maxime Coste.
On Thu, Jul 10, 2014 at 03:59:01PM -0700, Charlie Kester wrote:
> On Thu 10 Jul 2014 at 15:46:13 PDT Dimitris Papastamos wrote:
> >On Fri, Jul 11, 2014 at 01:43:16AM +0300, Dimitris Zervas wrote:
> >>First of all, we haven't even agree in which data structure will we use.
> >>Buffer gap, piece tabl
On Thu, Jul 10, 2014 at 11:45:07PM +0300, Dimitris Zervas wrote:
> On July 10, 2014 11:29:59 PM EEST, Evan Gates wrote:
> >> I will agree that it's super easy to implement and understand and it
> >covers most needs.
> >> But how about search?
> >> Is it fast?
> >
> >What about structural regular e
On Thu, Jul 10, 2014 at 09:33:53AM -0700, Charlie Kester wrote:
> The problem with linked lists of lines and piece tables has always been
> achieving good locality of reference. Not a problem with buffer gap,
> where locality was the main motivating factor behind the design.
In my experience, an
On Mon, Jul 07, 2014 at 09:39:36PM +0200, Anselm R Garbe wrote:
> On 7 July 2014 21:24, Maxime Coste wrote:
> > Seems to me you probably have tons of corporate copyright without knowing
> > it,
> > most software engineer contract specify that any code written by the
> &
On Mon, Jul 07, 2014 at 03:53:09PM +0200, FRIGN wrote:
> On Mon, 07 Jul 2014 15:37:05 +0200
> Michal Nazarewicz wrote:
>
> > I'm sorry, but no I'm not. The copyright is owned by Google. If you
> > cannot accept corporate copyright there's no point in me trying to get
> > the patch to be technic
Hello
On Tue, Jul 01, 2014 at 03:48:48AM +0300, Dimitris Zervas wrote:
> After a year or so in the list, I think each and every one is using tmux or
> screen (I think more tmux, but do not start a war please, that's not the
> subject).
> Why is that? For the tabs?
> Why not use tabbed? or DWM's
On Sun, Jun 29, 2014 at 05:34:50PM +0200, FRIGN wrote:
> On Sun, 29 Jun 2014 16:25:13 +0100
> Maxime Coste wrote:
>
> > Being written in C++11 (and depending on boost until the standard C++ regex
> > library gets widely available), it will probably not please everyon
On Sun, Jun 29, 2014 at 03:00:32PM +0300, Dimitris Zervas wrote:
> I think that a new text editor must be created, with text interface (and
> maybe GUI later).
Hello,
I have been working on an editor named Kakoune (http://github.com/mawww/kakoune)
that provides already a lot of that.
Being writ
30 matches
Mail list logo