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 Sun, Feb 14, 2016 at 03:17:35PM +, Maxime Coste wrote:
> 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 al
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 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
> nicely
I just implemented basic support for this with Shift-Tab in insert/rep
On Tue, Jan 19, 2016 at 04:14:55PM -0500, Matthew of Boswell wrote:
> On Tue, 19 Jan 2016 14:16:37 +0100
> Marc André Tanner wrote:
>
> > > - I also miss C-a and C-x for dealing with numbers .. but that's just a
> > > minor inconvenience right now
> >
> > These seem to be popular? I'm just u
Marc André Tanner writes:
> Is this still an issue? If so, please provide a failing example.
It works on gf850388 (just tested latest commit).
Thanks a lot!
> Thanks,
> Marc
>
> --
> Marc André Tanner >< http://www.brain-dump.org/ >< GPG key: 10C93617
On Tue, Jan 19, 2016 at 11:54:38PM +, Joshua Haase wrote:
> Filter has stopped working when selection is active since at least
> commit 304b645c974118b7 (haven't done a proper bisect to
> identify the issue).
>
> Will send a patch if I get this before someone else.
Is this still an issue? If
On Wed, Jan 20, 2016 at 07:47:27AM +0100, Markus Teich wrote:
> Marc André Tanner wrote:
> > There were some other (slightly ugly) changes necessary, but it should now
> > work as you want?
>
> In visual line mode it still behaves a little strange. Shifting right seems to
> work fine, but when shi
Heyho Marc,
Marc André Tanner wrote:
> > I don't know the best way to fix it, but it would
> > be possible to strip the newline from within the `cmd_set` function.
>
> I have taken this route for now. Should be fixed?
Yep, works.
> > Ah right, I see it's used for `~` now. Could you add this map
Matthew of Boswell writes:
> On Tue, 19 Jan 2016 14:16:37 +0100
> Marc André Tanner wrote:
>
> Haha, you wouldn't think such a minor "feature bloat" in vim would be
> so often used. I do the same thing... I a little annoyed when I use
> a vim emulator that doesn't have ctrl+a and ctrl+x support.
On Tue, 19 Jan 2016 14:16:37 +0100
Marc André Tanner wrote:
> > - I also miss C-a and C-x for dealing with numbers .. but that's just a
> > minor inconvenience right now
>
> These seem to be popular? I'm just using change or replace/overwrite for
> these use cases.
Haha, you wouldn't think
On Tue, Jan 19, 2016 at 01:56:32PM +0100, Marc André Tanner wrote:
> On Sun, Jan 17, 2016 at 07:59:50PM +0100, Silvan Jegen wrote:
> > On Sun, Jan 17, 2016 at 07:23:06PM +0100, Marc André Tanner wrote:
> > > The current source tree contains a `vis-open` shell script which
> > > provides basic file
On Mon, Jan 18, 2016 at 03:29:48PM +0800, Pickfire wrote:
> I really like vis, I just don't like it's support for multi-window.
> I can't resize it.
That is a deliberate design decision. At some point I would like to
experiment with a client/server architecture. Then your preferred window
manager
On Mon, Jan 18, 2016 at 08:24:14AM +0100, Jan Christoph Ebersbach wrote:
> Hi Marc,
>
> I like vis very much. It's blazing fast and comes with good defaults.
> The following things I noticed:
>
> - Setting defaults requires patching some c file instead of config.def.h
Are you referring to the w
On Sun, Jan 17, 2016 at 07:59:50PM +0100, Silvan Jegen wrote:
> On Sun, Jan 17, 2016 at 07:23:06PM +0100, Marc André Tanner wrote:
> > The current source tree contains a `vis-open` shell script which
> > provides basic file system navigation by means of fuzzy matching using
> > either slmenu or dme
> > > Still does not work. After enabling one of the `show` settings, I am
> > > unable
> > > to reset it again. I have to restart vis.
> >
> > Strange, seems to work fine here.
>
> Okay, I got the issue. `parse_bool` is called with `0\n` as first argument.
> The
> newline character should not
Heyho Jan,
Jan Christoph Ebersbach wrote:
> - Setting defaults requires patching some c file instead of config.def.h
have you tried the visrc.lua file in the repository root? You can do any `set`
command in there for your defaults. See my other mails in this thread.
> - It took me ages to start
I really like vis, I just don't like it's support for multi-window.
I can't resize it.
Is there any reason why vis won't implement libuv like neovim instead of
using an unactive project like libtermkey?
On Mon, Jan 18, 2016 at 08:24:14AM +0100, Jan Christoph Ebersbach wrote:
Since I'm using a l
Hi Marc,
I like vis very much. It's blazing fast and comes with good defaults.
The following things I noticed:
- Setting defaults requires patching some c file instead of config.def.h
- Background/Foreground colors are only applied when syntax highlighting
is possible for the currently loaded
Marc André Tanner wrote:
> > Maybe a global default 'syntax highlighter' applied regardless of file type
> > could do the job?
>
> Maybe, yes. However you probably want these features in combination with
> regular syntax highlighting. Maybe a layered approach would somehow work
Thats what I meant
> > > - How am I supposed to set my default theme/tabwidth/relativenumber/…
> > > settings? I could not find the option in config.h.
> >
> > By changing visrc.lua:
> >
> > vis.command('set ')
>
> Thanks, I missed that in the README. However there should be a few examples. I
> just tried to ins
On Sun, Jan 17, 2016 at 07:23:06PM +0100, Marc André Tanner wrote:
> On Sun, Jan 17, 2016 at 05:28:14PM +0100, Silvan Jegen wrote:
> > The command history buffer does not yet work correctly for me but I am
> > very glad to see the first version working for some cases already.
>
> Could you give a
On Sun, Jan 17, 2016 at 05:28:14PM +0100, Silvan Jegen wrote:
> The command history buffer does not yet work correctly for me but I am
> very glad to see the first version working for some cases already.
Could you give a few more details? What unexpected behaviour did you
encounter. As mentioned e
Heyho Marc,
Marc André Tanner wrote:
> On Sat, Jan 16, 2016 at 07:09:26PM +0100, Markus Teich wrote:
> > - Why did you choose to use full black instead of the base03 color from
> > solarized?
> >
> > - Even after "fixing" the above the colors don't look like solarized in any
> > way. If you don'
Hi Marc
I am enjoying vis a lot but the following missing functionality as
detrimental to my enjoyment...
On Sat, Jan 16, 2016 at 07:09:26PM +0100, Markus Teich wrote:
> Marc André Tanner wrote:
> > Did you (or anyone else) try it? First impressions? Which features did you
> > miss the most?
>
>
On Sat, Jan 16, 2016 at 07:09:26PM +0100, Markus Teich wrote:
> Marc André Tanner wrote:
> > Did you (or anyone else) try it? First impressions? Which features did you
> > miss the most?
>
> Heyho Marc,
>
> I built the standalone version and tried some stuff. I also went through my
> vimrc to fin
Marc André Tanner wrote:
> Did you (or anyone else) try it? First impressions? Which features did you
> miss the most?
Heyho Marc,
I built the standalone version and tried some stuff. I also went through my
vimrc to find any features I would like to use. Here are my comments in no
particular orde
On Sat, Jan 16, 2016 at 03:31:21PM +0100, Marc André Tanner wrote:
> This came up before[0]. libtermkey offers a sensible API and is reasonably
> simple (it consists of ~3 C files). The last release was in October and
> the latest commit 18 days ago. The replacement library, intended to provide
> s
On Fri, Jan 15, 2016 at 10:14:25PM -0800, Eric Pruitt wrote:
> On Fri, Jan 15, 2016 at 04:56:37PM +0100, Marc André Tanner wrote:
> > Did you (or anyone else) try it? First impressions? Which features did
> > you miss the most?
>
> I used Vis a while back when the project was still in its infancy,
On Fri, Jan 15, 2016 at 10:14:25PM -0800, Eric Pruitt wrote:
> [...] requires Lua 5.2+ which is too new to be in the latest Debian
> release.
I take that back; I just noticed that Lua is listed as an optional
dependency.
Eric
On Fri, Jan 15, 2016 at 04:56:37PM +0100, Marc André Tanner wrote:
> Did you (or anyone else) try it? First impressions? Which features did
> you miss the most?
I used Vis a while back when the project was still in its infancy, but I
can't compile the current release without fetching tarballs manu
On Thu, Dec 31, 2015 at 07:59:37PM +0100, Connor Lane Smith wrote:
> I think this is pushing it for a 2015 release. But I'll be sure to
> give it a go asap, 2016. :)
Did you (or anyone else) try it? First impressions? Which features did
you miss the most?
--
Marc André Tanner >< http://www.brai
I think this is pushing it for a 2015 release. But I'll be sure to
give it a go asap, 2016. :)
cls
Hi,
I'm pleased to announce the first release of vis, a vim-like editor:
http://www.brain-dump.org/projects/vis/vis-0.1.tar.gz
What started out with curiosity for an interesting data structure
evolved into my main text editor.
Some of vis' properties which might be interesting to some of you:
34 matches
Mail list logo
