Re: [dev] [bugs] st clears up upon resize and other little things

2016-01-19 Thread famfop
On 18/01/16 23:59, Brad Luther wrote: Will try to get my head around getting the Delete key to work on st now. Hi, what 'sh are you using? E.g. using mksh it worked out of the box (for me). As I'm using zsh I followed [0]. I suppose thats the cleanest way of doing it. _My_ problem now is, that

Re: [dev] [bugs] st clears up upon resize and other little things

2016-01-19 Thread Martti Kühne
On Tue, Jan 19, 2016 at 11:36 AM, famfop wrote: > > Hi, > what 'sh are you using? E.g. using mksh it worked out of the box (for me). > As I'm using zsh I followed [0]. I suppose thats the cleanest way of doing > it. _My_ problem now is, that some applications, e.g. ipython, don't > recognize the d

Re: [dev] [bugs] st clears up upon resize and other little things

2016-01-19 Thread Brad Luther
I'm using ash and it's not working out of the box. I'll see if I can find a patch or then I'll try using mksh, but I really like ash. Thanks for the tips. On Tue, Jan 19, 2016 at 8:36 AM, famfop wrote: > On 18/01/16 23:59, Brad Luther wrote: >> >> Will try to get my head around getting the Delet

Re: [dev] [ANNOUNCE] vis-0.1: first release of a vim-like editor

2016-01-19 Thread Marc André Tanner
> > > 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

Re: [dev] [ANNOUNCE] vis-0.1: first release of a vim-like editor

2016-01-19 Thread Marc André Tanner
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

Re: [dev] [ANNOUNCE] vis-0.1: first release of a vim-like editor

2016-01-19 Thread Marc André Tanner
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

Re: [dev] [ANNOUNCE] vis-0.1: first release of a vim-like editor

2016-01-19 Thread Marc André Tanner
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

Re: [dev] [bugs] st clears up upon resize and other little things

2016-01-19 Thread Roberto E. Vargas Caballero
On Tue, Jan 19, 2016 at 10:02:01AM -0200, Brad Luther wrote: > I'm using ash and it's not working out of the box. > I'll see if I can find a patch or then I'll try using mksh, but I > really like ash. > Thanks for the tips. The patch is not so complex ... Can someone put it in the wiki? diff --g

Re: [dev] [ANNOUNCE] vis-0.1: first release of a vim-like editor

2016-01-19 Thread Silvan Jegen
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

Re: [dev] [bugs] st clears up upon resize and other little things

2016-01-19 Thread Brad Luther
Roberto Vargas - it works in a perfect way! I have one question. Why didn't it work by default on ash? Is ash a sucky shell? Should I file a bug? Because by what I understand this is a hack, right? Not the ideal way. But so far it works really well! On Tue, Jan 19, 2016 at 12:33 PM, Roberto E. Var

Re: [dev] [ANNOUNCE] vis-0.1: first release of a vim-like editor

2016-01-19 Thread Matthew of Boswell
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

[dev] Re: Pseudo-3D shooter written completely in awk using raycasting technique

2016-01-19 Thread Black Rider
El Tue, 19 Jan 2016 02:08:16 -0200, Marc Collin escribió: > A friend told me about something you don't see every-day and I'm sure > people here are going to enjoy. [0] > It's a game inspired by the classic Wolfenstein 3D and Doom. The > novelty? It's a single awk file with ~650 lines of code. Wall

Re: [dev] [ANNOUNCE] vis-0.1: first release of a vim-like editor

2016-01-19 Thread Joshua Haase
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.

Re: [dev] [ANNOUNCE] vis-0.1: first release of a vim-like editor

2016-01-19 Thread Markus Teich
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

[dev] [vis] text_line_end() in insert mode

2016-01-19 Thread Markus Teich
Heyho Marc, something I don't seem to be able to figure out: When pressing the END key in insert mode, in vim the cursor moves after the last regular character in the current line, basically over the newline character, if you choose to display it. In vis however it does only move to the last regul

Re: [dev] [PATCH] Change an eprintf to a die to stop child from running its own slideshow

2016-01-19 Thread David Phillips
On Thu, Jan 14, 2016 at 09:47:37AM +, Dimitris Papastamos wrote: > On Thu, Jan 14, 2016 at 09:02:43PM +1300, David Phillips wrote: > > The child thread was created because execlp will not return if successful. > > The eprintf was placed after the call to execlp to catch any error, but the > > c

Re: [dev] [PATCH] Change an eprintf to a die to stop child from running its own slideshow

2016-01-19 Thread Markus Teich
David Phillips wrote: > On Thu, Jan 14, 2016 at 09:47:37AM +, Dimitris Papastamos wrote: > > On Thu, Jan 14, 2016 at 09:02:43PM +1300, David Phillips wrote: > > > diff --git a/sent.c b/sent.c > > > index fc5e389..88abe90 100644 > > > --- a/sent.c > > > +++ b/sent.c > > > @@ -153,7 +153,7 @@ fil

Re: [dev] [website] Project ideas page

2016-01-19 Thread Silvan Jegen
On Thu, Jan 14, 2016 at 07:16:14AM +0100, Anselm R Garbe wrote: > On 13 January 2016 at 21:34, FRIGN wrote: > > I must honestly say that I'm not convinced a GSoC would be a good influx > > of positive activity for suckless projects. > > It would have a good PR effect at least. > > > It takes a w