Re: [dev] [PATCH] Add tab-completion file-name expansion.

2014-07-06 Thread Martti Kühne
I feel honored and desecrated for suckless. But somebody obviously spent google's paid time on this and had, therefore, to note so in the license... xD

Re: [dev] [PATCH] [scron] Log to designated syslog facility

2014-07-06 Thread Dimitris Papastamos
On Sun, Jul 06, 2014 at 10:42:25PM +0200, Truls Becken wrote: > - openlog(argv[0], LOG_CONS | LOG_PID, LOG_DAEMON); > + openlog(argv[0], LOG_CONS | LOG_PID, LOG_CRON); Good catch! Applied.

[dev] [PATCH] [scron] Log to designated syslog facility

2014-07-06 Thread Truls Becken
--- crond.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crond.c b/crond.c index d416ece..2dbbb76 100644 --- a/crond.c +++ b/crond.c @@ -373,7 +373,7 @@ main(int argc, char *argv[]) TAILQ_INIT(&ctabhead); if (dflag == 1) { - openlog(argv[0], L

Re: [dev] [scron] simple cron daemon

2014-07-06 Thread Bigby James
> I don't see Ari whining over this, so why would you care? If you care about > the project and the direction it is taking, then start a technical discussion > or > even better demonstrate your ideas with patches! > > I am not here to satisfy all your needs or even provide context that I deem >

Re: [dev] [PATCH] Add tab-completion file-name expansion.

2014-07-06 Thread Ryan O’Hara
On Sun, Jul 6, 2014 at 12:25 PM, Alex-P. Natsios wrote: > Plus i have yet to see anyone use dmenu in that way. They can’t in the first place.

Re: [dev] [PATCH] Add tab-completion file-name expansion.

2014-07-06 Thread Alex-P. Natsios
On Sun, Jul 06, 2014 at 08:31:11PM +0200, FRIGN wrote: > > > I don't know about you guys but I don't want Google to infest the > license. Michal, either you join the license with your name only or > forget about the patch. > I've had very bad experiences with big companies having > licensing-

Re: [dev] [PATCH] Add tab-completion file-name expansion.

2014-07-06 Thread FRIGN
On Sun, 6 Jul 2014 14:31:56 -0400 Lee Fallat wrote: > I was actually going to ask about this too but held back; I'm assuming > that this patch will never be merged and people will only see that if > they apply this patch... And this is perfectly right! It's important to raise this issue. If you

Re: [dev] [PATCH] Add tab-completion file-name expansion.

2014-07-06 Thread Lee Fallat
I was actually going to ask about this too but held back; I'm assuming that this patch will never be merged and people will only see that if they apply this patch... What I was going to say: > A little off-topic here, but why was there a need to put: > +© 2014 Google Inc. > In the licence?...(just

Re: [dev] [PATCH] Add tab-completion file-name expansion.

2014-07-06 Thread FRIGN
On Sun, 06 Jul 2014 20:19:15 +0200 Michal Nazarewicz wrote: > Add a “-c” option which enables tab-completion for file-names. With > it enabled, when entered text contains multiple words (for example > “soffice docs”) or contains a slash (for example “~/bin”), pressing > C-i or Tab will expand th

Re: [dev] [PATCH] Add tab-completion file-name expansion.

2014-07-06 Thread Alexander Huemer
On Sun, Jul 06, 2014 at 08:19:15PM +0200, Michal Nazarewicz wrote: > +© 2014 Google Inc. // author: Michal Nazarewicz You should already have elaborated on this. Do it now. Kind regards, -Alex

[dev] [PATCH] Add tab-completion file-name expansion.

2014-07-06 Thread Michal Nazarewicz
Add a “-c” option which enables tab-completion for file-names. With it enabled, when entered text contains multiple words (for example “soffice docs”) or contains a slash (for example “~/bin”), pressing C-i or Tab will expand the last argument as a file name. If there were multiple expansions the

Re: [dev] [scron] simple cron daemon

2014-07-06 Thread Dimitris Papastamos
On Sun, Jul 06, 2014 at 09:33:29AM -0500, Bigby James wrote: > I can't speak for Dzen, but the wording of your first message in the thread > gave > me the same impression. We basically have two messages in the discussion > thread > to work with: One from the original author anouncing the project,

Re: [dev] [scron] simple cron daemon

2014-07-06 Thread Bigby James
On 07/06, Dimitris Papastamos wrote: > On Sat, Jul 05, 2014 at 09:30:25PM +0200, Džen wrote: > > On Sat, Jul 5, 2014 at 11:35 AM, Dimitris Papastamos wrote: > > > I've forked scron[0] [...] > > > > Why fork scron if you could just provide useful patches to the original > > author? > > Why do yo

Re: [dev] [scron] simple cron daemon

2014-07-06 Thread Dimitris Papastamos
On Sun, Jul 06, 2014 at 12:16:38PM +0200, Džen wrote: > Yes. That's why I was asking, I wanted to know the reason. It was purely because the original author did not feel like having duplicate code around, which I explained in my first e-mail. He was not going to drive the project in a different d

Re: [dev] [scron] simple cron daemon

2014-07-06 Thread Džen
On Sun, Jul 6, 2014 at 12:02 PM, Dimitris Papastamos wrote: > If you had, you would have seen that I already had merged ~20 patches > into the original repo which renders your question useless. Why useless? I was just wondering about the actual reason. I pulled scron from the original repo to try

Re: [dev] [scron] simple cron daemon

2014-07-06 Thread Dimitris Papastamos
On Sun, Jul 06, 2014 at 11:57:18AM +0200, Džen wrote: > On Sun, Jul 6, 2014 at 11:13 AM, Dimitris Papastamos wrote: > > And please next time look at the actually git history of the project > > before you jump in talking bs. > I did look at the git history, this doesn't change the reason why I > w

Re: [dev] [scron] simple cron daemon

2014-07-06 Thread Džen
On Sun, Jul 6, 2014 at 11:13 AM, Dimitris Papastamos wrote: > And please next time look at the actually git history of the project > before you jump in talking bs. I did look at the git history, this doesn't change the reason why I was asking. I was just wondering. Jump in talking bullshit. Yeah,

Re: [dev] [scron] simple cron daemon

2014-07-06 Thread Dimitris Papastamos
On Sat, Jul 05, 2014 at 09:30:25PM +0200, Džen wrote: > On Sat, Jul 5, 2014 at 11:35 AM, Dimitris Papastamos wrote: > > I've forked scron[0] [...] > > Why fork scron if you could just provide useful patches to the original > author? And please next time look at the actually git history of the p

Re: [dev] [scron] simple cron daemon

2014-07-06 Thread Dimitris Papastamos
On Sat, Jul 05, 2014 at 09:30:25PM +0200, Džen wrote: > On Sat, Jul 5, 2014 at 11:35 AM, Dimitris Papastamos wrote: > > I've forked scron[0] [...] > > Why fork scron if you could just provide useful patches to the original > author? Why do you assume that? I made a number of patches, I notifie