Re: [dev] A replacement for at.

2016-01-01 Thread Mattias Andrée
On Fri, 1 Jan 2016 10:19:01 +0100 Mattias Andrée wrote: > Hi! > > I'm written an alternative to at, called sat (for simple > at): https://github.com/maandree/sat sat is incompatible > with at, but I have tried to make sure that a > compatibility-layer can be written. > > sat is basically at wit

Re: [dev] A replacement for at.

2016-01-01 Thread Kamil Cholewiński
On Fri, 01 Jan 2016, Greg Reagle wrote: > On Fri, Jan 01, 2016 at 06:05:58PM +0100, Kamil Cholewiński wrote: >> Yes, please let's stop writing process management code into daemons and >> instead solve this problem in a portable and non-sucky way. > > It's called runit: http://smarden.org/runit/

Re: [dev] A replacement for at.

2016-01-01 Thread Mattias Andrée
On Fri, 01 Jan 2016 19:05:50 +0100 Kamil Cholewiński wrote: > > sat will create a PID file in $XDG_RUNTIME_DIR. > > PID files are a flawed concept, race conditions and > everything. Well. But they are standard. satd does not use the PID file to determine whether it is running, it uses flock.

Re: [dev] A replacement for at.

2016-01-01 Thread Greg Reagle
On Fri, Jan 01, 2016 at 06:05:58PM +0100, Kamil Cholewiński wrote: > Yes, please let's stop writing process management code into daemons and > instead solve this problem in a portable and non-sucky way. It's called runit: http://smarden.org/runit/

Re: [dev] A replacement for at.

2016-01-01 Thread Mattias Andrée
On Fri, 01 Jan 2016 18:05:58 +0100 Kamil Cholewiński wrote: > > Wouldn't you need a service supervisor with at's > > functionallity? > > No. Separation of concerns. > > > If you are paranoid about sat crashing > > When in doubt, assume the component will crash/fail. > > > as long as you c

Re: [dev] A replacement for at.

2016-01-01 Thread Kamil Cholewiński
> Wouldn't you need a service supervisor with at's functionallity? No. Separation of concerns. > If you are paranoid about sat crashing When in doubt, assume the component will crash/fail. > as long as you can have user-private services. Yes, please let's stop writing process management code i

Re: [dev][ubase][PATCH] fix several problems in dd

2016-01-01 Thread Roberto E. Vargas Caballero
On Fri, Jan 01, 2016 at 12:15:18PM +, Dimitris Papastamos wrote: > At the end of the day, a bug is a bug irrespective of how it was introduced. > > I will have a look at the patch tomorrow. My opinion is that all the code imported should be removed and written in house.

Re: [dev] A replacement for at.

2016-01-01 Thread Mattias Andrée
If you are paranoid about sat crashing and not get your jobs executed, it is possible to start sat under service supervision, as long as you can have user-private services. On Fri, 01 Jan 2016 15:17:43 +0100 Kamil Cholewiński wrote: > > satd is an unprivileged daemon that is user-private, and >

Re: [dev] A replacement for at.

2016-01-01 Thread Mattias Andrée
Wouldn't you need a service supervisor with at's functionallity? Are there any? If you want to do things really simply you can use sleep-until (https://github.com/maandree/sleep-until), but then you cannot as easily list jobs and run the before scheduled. On Fri, 01 Jan 2016 15:17:43 +0100 Kamil

Re: [dev] A replacement for at.

2016-01-01 Thread Kamil Cholewiński
> satd is an unprivileged daemon that is user-private, and > starts and exits automatically. Why not use a service supervisor?

Re: [dev][ubase][PATCH] fix several problems in dd

2016-01-01 Thread Dimitris Papastamos
On Fri, Jan 01, 2016 at 12:52:31PM +0100, FRIGN wrote: > On Fri, 01 Jan 2016 11:21:05 +0100 > isabella parakiss wrote: > > Hey Isabella, > > > i've been told on #2f30 that my opinion is void until i submit meaningful > > patches. this is a rant^Wbreakdown and fix of a random tool in ubase > >

Re: [dev][ubase][PATCH] fix several problems in dd

2016-01-01 Thread FRIGN
On Fri, 01 Jan 2016 11:21:05 +0100 isabella parakiss wrote: Hey Isabella, > i've been told on #2f30 that my opinion is void until i submit meaningful > patches. this is a rant^Wbreakdown and fix of a random tool in ubase I'll look deeper into this later, but I want to note here that back in th

[dev][ubase][PATCH] fix several problems in dd

2016-01-01 Thread isabella parakiss
i've been told on #2f30 that my opinion is void until i submit meaningful patches. this is a rant^Wbreakdown and fix of a random tool in ubase $ echo abcd | dd bs=1 count=1 skip=1 2>/dev/null # any other dd b $ echo abcd | ubase dd bs=1 count=1 skip=1 quiet; echo $? dd: copy: Success 22 "wtf i

[dev] [sbase][PATCH 2/4] ed: Reset modflag in clearbuf()

2016-01-01 Thread Roberto E. Vargas Caballero
For the same reason we don't care about the state of the buffer in clearundo() we can reset modflag in clearbuf(), because after calling it we don't want to know anything about the previous state. --- ed.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ed.c b/ed.c index 751e97

[dev] [sbase][PATCH 4/4] ed: Don't show size of files in no diagnosistic mode

2016-01-01 Thread Roberto E. Vargas Caballero
-s flag disables such warnings. --- ed.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ed.c b/ed.c index 1cf0d60..7e7fbb6 100644 --- a/ed.c +++ b/ed.c @@ -623,7 +623,8 @@ doread(char *fname) } inject(s); } - printf("%zu\n", cnt)

[dev] [sbase][PATCH 1/4] ed: Move modflag=0 to clearundo()

2016-01-01 Thread Roberto E. Vargas Caballero
When we discard the content of an undo buffer is because we don't need it anymore, and it means that we don't care about the modify state of the buffer so we can reset the modflag in clearundo(), and remove this assignation each time clearundo() is called. --- ed.c | 3 +-- 1 file changed, 1 inser

[dev] [sbase][PATCH 3/4] ed: add init()

2016-01-01 Thread Roberto E. Vargas Caballero
These funcction initializes the scratch buffer, and in case of having a file name parameter it loads the file in the scratch. It also fixes a problem before this version, where the saved filename was not set when the file didn't exist. --- ed.c | 32 ++-- 1 file changed

[dev] A replacement for at.

2016-01-01 Thread Mattias Andrée
Hi! I'm written an alternative to at, called sat (for simple at): https://github.com/maandree/sat sat is incompatible with at, but I have tried to make sure that a compatibility-layer can be written. sat is basically at without a lot of features that does not need to be there. sat is also written