Cc’ing the mksh list. Feel free to keep it, redirect there,
or remove it again.
Christoph Lohmann dixit:
>At least autoconf allows to specify a prefix, LDFLAGS or CFLAGS and some
A prefix is only needed when the Makefile installs; Build.sh accepts
the environment variables CC, CPPFLAGS, CFLAGS,
On Fri, May 31, 2013 at 2:35 PM, Fernando C.V. wrote:
> [...]
>
> But then on second though, since it's a separate process there would
> be problems with environment variables, and this might not have an
> easy solution.
Don't worry, even a simple `grep ... | while read l ; do ... ; x=a
; don
On Fri, May 31, 2013 at 2:05 PM, Fernando C.V. wrote:
> Would it make sense to create a whole shell infrastructure based on
> little small commands?
>
> I mean, not just replacing no-brainer builtin things like "echo", etc,
> but also things like "if", "while", "for", "set", by doing system()
> ca
Greetings comrades,
I have pushed some changes to st to fully support the 9 (X10 compatibil‐
ity), 1000 (button press), 1002 (report motion on press), 1003 (always
report motion) and 1004 (report focus) modes of xterm. The same move
bumps up the xfps so when some application is using mous
Greetings.
On Sat, 01 Jun 2013 12:38:25 +0200 Thorsten Glaser wrote:
> >wc -l Build.sh
> >2362
>
> An equivalent autoconf crap would be ten to hundred times
> that size, FWIW.
At least autoconf allows to specify a prefix, LDFLAGS or CFLAGS and some
options like to clean the build directory. Thi
[2013-05-31 10:23] Evan Gates
>
> > * ugly POSIX style
> > * backwards compatibility?
>
> I think it would be nice to have a simplest possible POSIX compliant sh.
> I'm not well versed in the options that already exist, is there a minimally
> compliant, smallest possible, POSIX sh?
AFAI
