You didn't mention what project this should apply to.
Hi, I use `git send-email`, it won't be mentioned by default.
It is for st. As you can see in the patch.
--
_
< Do what you like, like what you do. >
-
\ ^__^
\ (oo)\___
(__)\ )\/\
On Tue, 5 Jan 2016 17:38:16 +0800
Pickfire wrote:
> Hi, I use `git send-email`, it won't be mentioned by default.
> It is for st. As you can see in the patch.
I don't care what you use. Just stay with the ml etiquette and
mention the project name in the title of your bloody mail.
--
FRIGN
On Tue, Jan 05, 2016 at 10:42:52AM +0100, FRIGN wrote:
On Tue, 5 Jan 2016 17:38:16 +0800
Pickfire wrote:
Hi, I use `git send-email`, it won't be mentioned by default.
It is for st. As you can see in the patch.
I don't care what you use. Just stay with the ml etiquette and
mention the project
On Tue, 5 Jan 2016 17:44:12 +0800
Pickfire wrote:
> I doesn't know there is an ml etiquette, I will add it to the wiki.
> It isn't mentioned.
Not everything is written in the wiki man, and it's not the first time
you sent in a patch.
You know how patch-mails are formatted, so that's how you can
On Tue, Jan 05, 2016 at 05:38:16PM +0800, Pickfire wrote:
> Hi, I use `git send-email`, it won't be mentioned by default.
See the git-send-email manpage. There is a way to modify the
subject.
On Tue, Jan 05, 2016 at 05:44:12PM +0800, Pickfire wrote:
> On Tue, Jan 05, 2016 at 10:42:52AM +0100, FRIGN wrote:
> >>Hi, I use `git send-email`, it won't be mentioned by default.
> >>It is for st. As you can see in the patch.
> >
You can use git send-email --subject-prefix='st][PATCH'
On Tue, Jan 05, 2016 at 10:49:36AM +0100, Roberto E. Vargas Caballero wrote:
On Tue, Jan 05, 2016 at 05:44:12PM +0800, Pickfire wrote:
On Tue, Jan 05, 2016 at 10:42:52AM +0100, FRIGN wrote:
>>Hi, I use `git send-email`, it won't be mentioned by default.
>>It is for st. As you can see in the pat
commit b52f376a0f18db0dc8b2c8707cf3f41d32fd9a10
Author: FRIGN
AuthorDate: Tue Jan 5 11:10:39 2016 +0100
Commit: FRIGN
CommitDate: Tue Jan 5 11:10:39 2016 +0100
Update example in farbfeld.5
We were close to a full program anyway, so I just completed the code so
you can st
commit b669c8642e21850ea561931633ae06e6ba5bf354
Author: FRIGN
AuthorDate: Tue Jan 5 11:16:11 2016 +0100
Commit: FRIGN
CommitDate: Tue Jan 5 11:16:43 2016 +0100
farbfeld.5: exit() -> return
Now that we're in main, we don't need to exit().
Also, we should return 0 at the e
Thanks to voidead: god of destroying ""
---
config.def.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.def.h b/config.def.h
index fd09d72..c11ed2f 100644
--- a/config.def.h
+++ b/config.def.h
@@ -127,7 +127,7 @@ static unsigned int mousebg = 0;
* will reverse too
Let's put there the default foreground color.
http://www.nickkolenda.com/wp-content/uploads/2015/10/color-arousal.png
Thanks to voidead for the idea.
---
config.def.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.def.h b/config.def.h
index fd09d72..c11ed2f
These tools are not part of POSIX, but they were part of the original
UNIX and even today they are still wide used. The work done by this
tools can be done by grep, so this implementation is only masking the
code with different names to get the work done.
---
Makefile | 4 +++-
grep.c | 5 +
Greetings.
On Tue, 05 Jan 2016 14:09:04 +0100 Ivan Tham wrote:
> Thanks to voidead: god of destroying faggot asscunts
What’s the rationale of this patch? He complained without any manners on
IRC that st is completely buggy and it’s showing in his misconfigured
system italics as yellow.
I
I am sorry for that, I had removed that malicious word in another patch.
--
_
< Do what you like, like what you do. >
-
\ ^__^
\ (oo)\___
(__)\ )\/\
||w |
Greetings.
On Tue, 05 Jan 2016 14:11:11 +0100 Ivan Tham wrote:
> Let's put there the default foreground color.
> http://www.nickkolenda.com/wp-content/uploads/2015/10/color-arousal.png
> Thanks to voidead for the idea.
As said in my answer before: »I don’t like yellow, it arouses
Hey,
On 5 January 2016 at 14:01, Roberto E. Vargas Caballero wrote:
> These tools are not part of POSIX, but they were part of the original
> UNIX and even today they are still wide used. The work done by this
> tools can be done by grep, so this implementation is only masking the
> code with dif
On Tue, Jan 05, 2016 at 02:35:18PM +0100, Connor Lane Smith wrote:
> Hey,
>
> On 5 January 2016 at 14:01, Roberto E. Vargas Caballero
> wrote:
> > These tools are not part of POSIX, but they were part of the original
> > UNIX and even today they are still wide used. The work done by this
> > too
commit eeeb7a6e53ae54b795f47131bf36227d6fd3fe87
Author: Quentin Rameau
AuthorDate: Tue Jan 5 14:52:46 2016 +0100
Commit: sin
CommitDate: Tue Jan 5 13:54:17 2016 +
grep: make E and F flags mutually exclusive
Don't make F the priority flag when both E and F are given, inst
commit 24c4b045fc495becc9ba4239ba3d2963851c7634
Author: FRIGN
AuthorDate: Tue Jan 5 16:38:12 2016 +0100
Commit: FRIGN
CommitDate: Tue Jan 5 16:38:12 2016 +0100
Add tool manpages and set up the Makefile to install the manuals
While at it, refactor the makefile a bit.
diff --
commit ba154494ae239b9a79fc0947cad497e983c80653
Author: FRIGN
AuthorDate: Tue Jan 5 16:03:43 2016 +0100
Commit: FRIGN
CommitDate: Tue Jan 5 16:03:43 2016 +0100
2ff: Check return values and handle errors
Also, in case convert(1) is not in the path, it will just return an
commit a7dba356ecad56b84c06fc12f537682feff61232
Author: FRIGN
AuthorDate: Tue Jan 5 16:56:47 2016 +0100
Commit: FRIGN
CommitDate: Tue Jan 5 16:56:47 2016 +0100
Fix Makefile+config.mk
I forgot that we can't just cd. It has to be a &&-statement.
Also, uncomplicate the outp
commit 37279aea00503196cfb5e008b66ced8ec8043e1f
Author: FRIGN
AuthorDate: Tue Jan 5 17:13:38 2016 +0100
Commit: FRIGN
CommitDate: Tue Jan 5 17:14:02 2016 +0100
Quote paths in Makefile
Thanks quinq for reporting this!
diff --git a/Makefile b/Makefile
index cfc4fe8..46dcefc 1
commit 4e84440473323aa72109162123ff062a198a2c44
Author: FRIGN
AuthorDate: Tue Jan 5 17:31:43 2016 +0100
Commit: FRIGN
CommitDate: Tue Jan 5 17:31:43 2016 +0100
Use consistent {} in Makefile
diff --git a/Makefile b/Makefile
index 46dcefc..789f817 100644
--- a/Makefile
+++ b/Makefile
commit 226d9136b89ac6f714ff5e9d67dea278f149bedd
Author: FRIGN
AuthorDate: Tue Jan 5 17:47:16 2016 +0100
Commit: FRIGN
CommitDate: Tue Jan 5 17:47:16 2016 +0100
Also be consistent in config.mk
diff --git a/config.mk b/config.mk
index 9d01b31..f123dc1 100644
--- a/config.mk
+++ b/conf
commit b1868127e4102b2e073750c7f55fd445bee028be
Author: FRIGN
AuthorDate: Tue Jan 5 20:41:57 2016 +0100
Commit: FRIGN
CommitDate: Tue Jan 5 20:41:57 2016 +0100
Fix 2ff stderr-redirect
Thanks izabera for spotting this!
diff --git a/2ff b/2ff
index 19946df..6d89499 100755
---
26 matches
Mail list logo
