On Sat, Sep 13, 2014 at 11:06:33AM -0400, Andrew Hills wrote:
> Hi Marc,
>
> Thank you for the thorough and illustrated RFC. If you have not already
> done so, I suggest you keep this text around with the project.
Good idea, I've added it as README for now.
> > Notice that the common case of app
On Sat, 13 Sep 2014 10:09:23 -0700
Markus Teich wrote:
> I find the vim style completion pretty handy. It just completes words, which
> it
> already knows (from open/included files), so you don't need to implement
> complex
> language- and context-dependent filtering. This can also be used when
Andrew Hills wrote:
> >+ code completion: this should be done as an external process. I will
> > have to take a look at the tools from the llvm / clang project. Maybe
> > dvtm's terminal emulation support could be reused to display an
> > slmenu inside the editor at the cursor p
Marc André Tanner wrote:
> For word, sentence and paragraph there is no difference between the inner
> and normal variants.
Heyho Marc,
there should be a difference. For example you normaly want to use the inner
variant with the change operator and the normal (outer) variant with the delete
o
On Sat, Sep 13, 2014 at 05:25:32PM +0200, Silvan Jegen wrote:
> In my brief testing I found that H, M, L (in Vim: moving the cursor to
> the first, middle or last line of a window) are not implemented
They were easy enough to add, should work now.
> and that G does not move the cursor to the end
FYI, anyone building on OpenBSD (and possibly other BSDs), add
-D_BSD_SOURCE to CFLAGS in config.mk for SIGWINCH.
On Sat, Sep 13, 2014 at 04:01:15PM +0200, Marc André Tanner wrote:
> TLDR: I'm writing an experimental but (hopefully) highly efficient vim
> like text editor based on a piece chain data structure. You will find
> an url to a git repository at the end of this rather long mail.
I tested the editor
On Sat, Sep 13, 2014 at 04:39:15PM +0200, Christian Neukirchen wrote:
> Marc André Tanner writes:
> > TLDR: I'm writing an experimental but (hopefully) highly efficient vim
> > like text editor based on a piece chain data structure. You will find
> > an url to a git repository at the end of this
Hi Marc,
Thank you for the thorough and illustrated RFC. If you have not already
done so, I suggest you keep this text around with the project.
> Notice that the common case of appending text to a given piece is fast
> since, the new data is simply appended to the buffer and the piece length
> is
On Sat, 13 Sep 2014 16:01:15 +0200
Marc André Tanner wrote:
Hey Marc,
> TLDR: I'm writing an experimental but (hopefully) highly efficient vim
> like text editor based on a piece chain data structure. You will find
> an url to a git repository at the end of this rather long mail.
your mail mad
Marc André Tanner writes:
> TLDR: I'm writing an experimental but (hopefully) highly efficient vim
> like text editor based on a piece chain data structure. You will find
> an url to a git repository at the end of this rather long mail.
Funny, I just thought tonight about a variant of vi where
TLDR: I'm writing an experimental but (hopefully) highly efficient vim
like text editor based on a piece chain data structure. You will find
an url to a git repository at the end of this rather long mail.
Help welcome!
Why another text editor?
It all started when I was
On Fri, 12 Sep 2014 18:50:34 -0700
Eric Pruitt wrote:
> Does anyone happen to have a patch implementing SSL support for quark
> that they haven't posted to the wiki?
As Andrew already rightfully said, the way to go with quark is via
stunnel.
Implementing ssl into quark directly would kind of be
13 matches
Mail list logo
