VT102ID is the sequence that the terminal returns when it is inquired
to identify itself. This value should be configurable in the same
way that another st parameters.
---
config.def.h | 3 +++
st.c | 8 +++-
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/config.def.h
Quick style fix.
From c15536a34a5c61ac4c1899e1368c8cb0f1c0a505 Mon Sep 17 00:00:00 2001
From: sin s...@2f30.org
Date: Fri, 15 Aug 2014 14:54:03 +0100
Subject: [PATCH] Do not indent switch cases
There's only one way to format switch statements.
http://cm.bell-labs.com/cm/cs/who/dmr/ctut.pdf -
It is already pushed. You can test it.
I don't have linux installed. However, I have applied the patch on my
OS X port, and although development is in a very early phase, it seems
to function as normal (briefly using vim and emacs and bash within my
terminal).
Thanks.
-Steven
Steven, when you first disclose your project publicly, please adjust the
proper License requirements.
From what I see, it looks like you stripped everything of the codebase
and previous structure.
Amadeus,
I will certainly move all the license files back when it is publicly
released. All I've done right now is moved all the files out of the
root directory into a subdirectory, so that people don't mistakenly
think the port is ready for any kind of use.
-Steven
On Fri, Aug 15, 2014 at
No.
Github isn't a workbench that is public by accident. By uploading to
Github you release your project to the public. Start treating it that
way and start treating projects you incorporate into your code in a
way that makes you look like a responsible human being.
cheers!
mar77i
On Fri, Aug 15, 2014 at 12:35:06PM -0300, Amadeus Folego wrote:
Steven, when you first disclose your project publicly, please adjust the
proper License requirements.
From what I see, it looks like you stripped everything of the codebase
and previous structure.
I don't understand what the
Do we sound like we want an additional clause in the license?
Addendum: In case source files are split from this license document in
a different directory structure, help us find the license by noting
the path with huge ASCII-art characters in every affected source file.
cheers!
mar77i
On Fri, 15 Aug 2014 15:00:03 +0100
Dimitris Papastamos d...@spl9.org wrote:
Quick style fix.
Thanks! Applied.
Cheers
FRIGN
--
FRIGN d...@frign.de
