Followup-To: miros-mksh list (which includes miros-discuss list)
Andrew Kudryashov dixit:
cc (Ubuntu/Linaro 4.7.2-2ubuntu1) 4.7.2
Use a different version of the compiler. The workaround I applied
to the Debian packages is not really ripe for consumption, and
relies on the user TESTING THE
Andrew Kudryashov dixit:
Attached is a hackish workaround for small completion
bug that leaves glob noise if non-existent file is matched
and tilde expansion is performed at the same time.
OK, thanks for the problem analysis and first draft of a fix.
You were fully correct, but I could solve it
Carsten Peter dixit:
After running myscript.ksh my shell console seems to be smashed. No
carriage return seems to be done anymore when pressing the return key.
Any characters entered on the shell prompt aren't shown anymore too.
This doesn’t happen for me, even on GNU/Linux at work.
On the other
Roy Tam dixit:
I installed the RPM from the Oracle Linux 6.1 ISO image named
mksh-39-5.el6.x86_64.rpm. I also tried to install a newer version of
Well… I don’t have that. I assume it’s RHEL based, but then,
I don’t have that either. So if you could please point me to
ideally the SRPM and
Dixi quod…
as I’m not likely to continue hacking tonight
Plan is to add tty_fd tracking (so COLUMNS and LINES are
continuously updated, even in scripts such as uhr, without
the need to use stty), test, then release R41.
SO PLEASE TEST! This includes HP-UX, OSF/1, ULTRIX, and
many more.
Thanks,
Steffen Daode Nurpmeso dixit:
But we're deep in a very complicated program, right?
Right.
I thought about digging into and sending patches for
- no tab completion over / boundary in upward direction
Eh, *what*?
- no tab completion in the middle of a word (for partial word before cursor)
Steffen Daode Nurpmeso dixit:
ok for a login shell to simply ignore them; just as mksh(1) R40
did ? ;)
There were no signal handling related changes since R40, at least
none in that area.
bye,
//mirabilos
--
„nein: BerliOS und Sourceforge sind Plattformen für Projekte, github ist
eine
Dan Douglas dixit:
For $@ that sounds about right. I think it would be preferable if x=$@ and
x=$@ were the same. If a user wants IFS-delimited they should probably use
Turns out you’ll get them being the same:
• foo $@ uses the unquoted $@ inside a quoted string,
not the quoted $@,
Hugues Moretto-Viry dixit:
If you have enough time, I would appreciate it.
Sure, no problem.
The PS1 included in the previous email ends with \e[0m. As you said it, the
changes are small.
I also added a little description, maybe you'll need it.
OK ;-)
PS: Feel free to re-bounce these mails to
Hugues Moretto-Viry dixit:
Your PS1 conversion was useful. I tried it but now it says above my PS1:
mksh: read-only:
read-only what?
set -x might help.
If I understand correctly, the bash syntax \[\e[1;34m\] is replaced in
mksh by: \a\e[1;34m\a.
Not exactly…
About blackslash expansions (\r,
Hugues Moretto-Viry dixit:
First, sorry for the empty message but new Google message interface is
pissing me off...
Ah, best to avoid Google altogether…
About set -x, here a more verbose output:
+ typeset d=/home/mad p=~[[ = ?(*/) ]]
mksh: read-only:
Okay, I see.
You did the mistake of
Finn Thain dixit:
For some time I have been meaning to check out mksh, and your email
prompted me to install it. The first thing I noticed was how good the
documentation is (the bash man page is missing a lot of stuff).
Great! Most of the manual page was not written by me, mind you,
standing
Hi everyone,
I seem to recall promising an eMail whenever a new release
of mksh is out. Et voilà, enjoy “doch!”:
https://www.mirbsd.org/permalinks/wlog-10_e20130426-tg.htm
I’ve uploaded it to The MirPorts Framework, the OpenSuSE
Buildservice and Debian unstable already. I guess raring
people
Anselm R Garbe dixit:
Can you elaborate on this functionality a bit that mksh provides, but
pdksh doesn't?
Not easily; the last release of pdksh was in 1999, and mksh is
actively developed; even pointing out every single bugfix, for
POSuX compliance or genuine, would take several Kibibytes.
Dixi quod…
I’ll change this to not abort for interactive shells then.
Actually, I cannot reproduce that it causes an interactive
shell to exit, neither like this…
tg@blau:~ $ mksh -ic 'unset KSH_VERSION; echo $?,foo'; echo $?
mksh: read-only: KSH_VERSION
1,foo
0
tg@blau:~ $ mksh -lc 'unset
Steffen Daode Nurpmeso dixit:
|Please, if you patch mksh, append a space and a “vendor string”
|to KSH_VERSION, like PLD:
It's really only private (but it's git(1), i'll adjust the patch).
Sure but as you can see it helps not confusing your version
with upstream unpatched versions.
Thanks,
oneofthem dixit:
Wow, thanks. I didn't expect such an in depth response.
You’re welcome ☺
I hope that this response will show up on search engines
and help other coders, too, that’s why it was a tad lengthy.
I think it can be extended even, e.g. with actual examples
plus citations of the ISO C
oneofthem dixit:
If you shouldn't use signed ints, then how do store negative numbers?
Basically, if you have something negative, you store it
either in a signed int, or in a typedef union {
mksh_ari_t i;
mksh_uari_t u;
} mksh_ari_u;
(where ari_t and uari_t are the signed and
Jens Staal dixit:
I have not looked at it yet - did the build-on-plan9 modifications
Oh, sorry… they’re probably lost in my INBOX.
Can you rebase them against R47 and send to me again (off-list to
save traffic) for the next version?
I have uploaded an archive that is intended to be extracted
Steffen Daode Nurpmeso dixit:
maybe this test would be worth adding to check.t.
I think i do assume the correct behaviour.
Indeed. A bit late, but I applied the testsuite part
(not the dot.mkshrc part because I don’t think that
should be default) with only very minor changes
(basically, put it
Fabian Greffrath dixit:
introduction that assumes nothing has been installed yet,
There should be an msys.bat in your mingw directory. Run this with the
I don’t even have one ☺ but …
Get the lates installer from here to install MinGW/MSYS:
… this helps, of course – thanks.
All that
Hi everyone,
today I’m also loudly announcing a jupp release, even though
it’s “contrib” for MirBSD, just because it fixes several data
corruption (on ^K/) and crash bugs.
And if you hadn’t noticed already, mksh R48b fixes a display
issue for multi-line prompts when resizing windows.
Credits:
Steffen Daode Nurpmeso dixit:
?1[steffen@sherwood]$ kill -STOP %1
Why STOP and not TSTP? (Not related, but curious.)
?0[steffen@sherwood]$ kill -CONT %1
The kernel does not communicate this to the shell,
so it assumes the job is still stopped and thus
out of job control. If you “bg”, it
Steffen Daode Nurpmeso dixit:
Hah. The fun starts on a non-UTF-8 tty:
Well that much should be obvious: it’s not permitted to store
raw octet filenames in a filesystem that requires Unicode
canonical decomposed filenames. (I think this also violates
some standard, somewhere.)
And when mixing
Earnie Boyd dixit:
Try using something like 「print -r -- $PATH」 instead.
Yes, that does the job of issuing the string without translation of
characters by escape sequence. There are however a lot of scripts
using echo.
Mhm. One thing you can do is force the POSIX echo.
Ah well – that’s mksh
Todd C. Miller dixit:
I don't think there is a way for a process to be notified via SIGCHLD
when a child process receives SIGCONT. So unless you are already
in waitpid() with WCONTINUED set you won't see it.
OK, thanks for confirming though.
bye,
//mirabilos
--
I believe no one can invent an
Steffen Daode Nurpmeso dixit:
I think i've misread what you said and also misunderstand;
[…]
I do not understand your mail at all… sorry but I think
we have a language or conceptual barrier here?
bye,
//mirabilos
--
20:49⎜«Natureshadow» Oops, jetzt hab ich mir doch glatt beim Trinken
⎜
Earnie Boyd dixit:
One can use either method as long as a method doesn't give unexpected
results to the end user. If you translate PATH to / then you need to
translate it back to \ before spawning a process because Windows OS
will not do the right thing with / in PATH.
Hrm. Well, maybe for
Uh guys, one thing in front: please stop Ccing me when mailing the list.
I’ve read today that the -F option of ls(1) is _really_ slow
in Cygwin (and related environments). I’m asking my packagers
to patch dot.mkshrc for those environments if that is indeed
true:
-alias l='ls -F'
+alias l='ls'
Dave Jones dixit:
The response at the time was:
To be honest,
I'm actually opposed to persistent history files anyway
But obviously that is now possible...
They were always possible.
So the question is if timestamping somehow possible now or is it a feature I
can request again {ex. export
Chris Sutcliffe dixit:
Not sure if my mailer killed the escape sequences or not, but I don't see
any '\r' in the example you provided.
OK, then let’s send the stuff either uuencoded, or use the
generic $'…' escaping form.
to colour the return code red, if I understand correctly, I should do:
Chris Sutcliffe dixit:
Thanks for the offer, below is my ps1 prompt based on the latest
dot.mkshrc example where I'm trying to change the return code to red:
OK, we can do this even without uu as it contains no magic chars.
Use something like this:
(( e ))
Chris Sutcliffe dixit:
Does it have something to do with the escape sequences being used inside
Oh, ouch.
(( e )) REPLY+=$'\''\1\e[31m\1'\''$e|$'\''\1\e[0m\1'\''
an inline function?
It’s not a function, it’s a single-quoted string… at that time, anyway.
Sorry about that.
bye,
Chris Sutcliffe dixit:
I don't find it that slow, but if there is enough complaints about it, I
Hmm. I can measure that a bit on my win2k installation (which is
slow enough, hardware-wise, to be able to get representative data,
even if most people would run faster systems). I’ll get back to you.
Steffen Daode Nurpmeso dixit:
i reproducibly fail to reproduce it, but regulary, once in a while
Yeah, I get it occasionally too and cannot reproduce it – it’s been
like that for years. Last time I had it when I was mplayering a radio
stream and pkill’d it, but that is not reproducible right
Seb dixit:
It seems there is a problem in the way the R48b deals with the
spaces in the variables. Below is a piece of code showing the strange
Thanks for bringing this to my attention. Indeed, there appears to be
field splitting not done correctly, but at least it’s not m̲y̲ fault ☺
Steffen Daode Nurpmeso dixit:
+ cb.c_iflag = ~(ISTRIP);
OK, applied. Thanks.
bye,
//mirabilos
--
„Also irgendwie hast du IMMER recht. Hier zuckelte gerade ein Triebwagen mit
der Aufschrift Ostdeutsche Eisenbahn durch Wuppertal. Ich glaubs machmal
nicht…“
Stefan Heine dixit:
on pdksh, I get an output showing one multi-line entry:
[...]
16 echo
foo
bar
That is not pdksh.
tg@blau:/tmp/p/pdksh-5.2.14 $ PS1='x ' pdksh
x echo a
b
a
b
x set -o emacs
x history
1 echo a
2 b
3 set -o emacs
Another thing,
Guido Berhoerster dixit:
Hmm, I've done a bit more testing, sometimes it works, sometimes
it does not
Right, it’s not reliable. All I can tell you is that they
synchronise with $HISTFILE upon pressing Enter (which implies
that order may be important).
use the same $HISTFILE but one seems to
Benny Siegert dixit:
I have a small question about mksh. In bash on GNU/Linux, a feature
Or in GNU bash on MirBSD…
that I really like is that Ctrl+L clears the screen. I am not saying
that this should be the default behaviour on mksh as well but: is
there any way that you can get this in mksh?
Vincent Lefevre dixit:
I hate this feature because of the ambiguity with decimal, but
Indeed. It does break traditional Korn shell scripts; I believe
this to be the second-largest mistake in recent POSIX/shell.
The ambiguity happens often enough when dealing with zero-padded
dates (e.g. in
Vincent Lefevre dixit:
Well, that's very confusing, because both ksh93 and mksh are
ksh alternatives. This can break scripts with #!/bin/ksh.
ksh93 can break scripts with #!/bin/ksh because interpreting
leading-digit-zero numbers as octal is a *very* recent change,
and is *known* to break
Rob dixit:
I've been working on a C compiler in my spare time and recently finished
[…]
If anyone's interested. It's hosted here [1] and I'm all ears to
critiques and feedback.
1: https://github.com/bobrippling/ucc-c-compiler
Cool! I’ll probably play with it some time.
By the way: just
Markus Teich dixit:
I am using mksh for nearly a year now, but only recently I noticed some weird
behaviour with the history file. When I have multiple pts open and enter a
Command in one of them, it can't be found in the history of the others.
It can, if you press Enter in the other shell.
Philipp von Bassewitz dixit:
vi mode is very fine for me. I hope it will be available for a long time even
without UTF-8 support. A small hint in the man page would be helpful, like:
OK, will do. (The headers were fine this time, thanks. It had only
In-Reply-To but not References, which works
Bert M�nnich dixit:
$ arr=(foo bar)
$ readonly arr
$ arr=bla
Is this a bug, or am I missing something? I've also checked `typeset
-r arr[*]' which shows the same behaviour.
Thanks for the report; this seems to be a bug in the code we
inherited from pdksh indeed. Will fix.
bye,
//mirabilos
renkel dixit:
How do I get mksh to envoke the ENV file in called programs?
The initial program envoked gets it,
but programs it call do not
Eh…
… I’m not sure I understand what you want from me, but
${ENV:-~/.mkshrc} processing is done by interactive shells,
as documented in the manual page.
dem...@arcor.de dixit:
wie sieht es mit einer verwendung der bsd editline library in der
mksh aus ? ich wuerde das sehr begruessen, editline ist doch den
eingebauten funktionen ueberlegen.
Genaues Gegenteil: die eingebauten Funktionen sind deutlich besser,
fehlerfreier, und können UTF-8.
Jacko dixit:
das war von mir auch nur ne vermutung, da sich die tcsh wesentlich
geschmeidiger
Hm, tut sie? Keine Ahnung… tcsh klingt nach FreeBSD…
in der beziehung verhaelt und libedit doch aus ihr
gewonnen wird.
Huh?
AUTHORS
dem...@arcor.de dixit:
The editline library was written by Christos Zoulas. Luke Mewburn wrote
^^^
dieser NetBSD entwickler ist
seit vielen jahren der maintainer der tcsh.
Ah okay, wußte ich nicht.
(man
Ryan Schmidt dixit:
Hello, I'm a developer with the MacPorts project. An mksh package was
submitted to MacPorts today, and I just committed it.
Thank you very much!
So if you wanted to list that on your web site, you could do that.
OK will do.
You currently list Homebrew and Fink packages,
Ryan Schmidt dixit:
Oh, I see now, yes, hwprefs does exist on older Mac OS X systems. But
a survey of my systems says it only existed on Intel Macs running Mac
OS X 10.4, 10.5, and 10.6 -- not later Intel systems, and not earlier
PowerPC systems -- so it's not terribly portable.
Right – I used
Bert M�nnich dixit:
Is this a bug, or am I missing something? I've also checked `typeset -r
arr[*]'
Fixed in CVS: MIRBSD KSH R49 2014/05/27
Thanks for the report,
//mirabilos
--
“ah that reminds me, thanks for the stellar entertainment that you and certain
other people provide on the Debian
Ryan Schmidt dixit:
which you can get with $CC -v. (Depending on the version of OS X and
We have $CC -v in some other place already, but I’ve added all
the others for now (in mksh CVS HEAD).
Thanks for your contribution,
//mirabilos
--
„Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein
Hi *,
we’ve got new versions. (This eMail is for those who asked for it.)
https://www.mirbsd.org/permalinks/wlog-10_e20140629-tg.htm
bye,
//mirabilos
PS: Also on my list, but need some serious hacking time more:
mksh-in-Android (testing and submission), paxmirabilis, m4,
mircksum,
Ivan Delalande dixit:
In rare occasions, when invalid UTF-8 sequences are present in the
command line buffer, the loop in x_zots() loops indefinitely because we
have str xlp and x_col == xx_cols, so the condition for the loop
Ouch. Thanks for noticing.
will be true, but the actual code that
michael dixit:
So far so good. Seems on par with dash's quickness and far more capable. I
Right. More robust (and less buggy), too.
just wish I could get to the next line with CTRL-V CTRL-J. It's a stupid
There is no “next line” in mksh, at least not interactively.
But with ^Xe, you can
Steffen Nurpmeso dixit:
just stumbled over a makefile which does
Fix that Makefile.
bye,
//mirabilos
--
13:37⎜«Natureshadow» Deep inside, I hate mirabilos. I mean, he's a good
guy. But he's always right! In every fsckin' situation, he's right. Even
with his deeply perverted taste in software
ban...@openmailbox.org dixit:
Hello, I wanted to ask a few questions about the security of mksh. We are
currently debating its use over GNU bash in our anonymity-centric distro
Whonix, in a very security sensitive package. It appears the closest thing to
That’s nice. Thank you for asking. I
Lorenzo Beretta dixit:
The $RANDOM variable should not be exported: it's useless, and it may
fool scripts that try to detect if the shell provides it.
This is an upstream decision, please continue this either on
the mailing list (Cc’d) or (if you really must) the Launchpad
tracker.
Actually,
Hi David,
I’m having a slight problem (shbot runs ksh93 when asked “k#”):
19:06⎜mirabilos:#ksh k# nameref x=y; y=z; echo $x,$y; unset x; echo $x,$y
19:06⎜«shbot:#ksh» mirabilos: z,z
19:06⎜«shbot:#ksh» mirabilos: ,
19:06⎜mirabilos:#ksh k# nameref x=y; y=z; echo $x,$y; nameref x=; echo $x,$y
Dixi quod…
Hi David,
Nevermind…
19:22⎜mirabilos:#ksh 550 5.1.1 d...@research.att.com: Recipient address
rejected: User unknown in local
⎜recipient table
19:23⎜«jilles:#ksh» mirabilos, yes, dgk and gsf don't work there anymore
Right now, I believe using 'nameref x=' to un-nameref it
tl;dr: We probably should simplify the code (no promises
about $RANDOM other than its value area) and not export
$RANDOM any more, and only use arc4random-related functions
where really convenient, “lesser” OSes are SOL. We move
the task to get better random numbers on the script writers
(and
Dixi quod…
Right now, I believe using 'nameref x=' to un-nameref it
Nevermind this either…
R50c coming up…
… or this.
20:21⎜mirabilos:#ksh m# nameref x=y; y=z; echo $x,$y; typeset +n x; echo $x,$y
20:21⎜«shbot:#ksh» mirabilos: z,z
20:21⎜«shbot:#ksh» mirabilos: y,z
Thanks to ormaaj for
Jason Spiro dixit:
By the way, do here-documents work okay on modern versions of Android?
Or is there no place for mksh to write the required temporary files to
make them work?
There is still no place. If you set (not even needed to export, but
exporting is better so subshells inherit it)
Jason Spiro dixit:
If I may ask: How do you test mksh on Android?
I boot up a VM at work (where I have sufficient space),
which runs just the recommended AOSP build environment.
Inside that, I build it, then I run “emulator” over VNC.
Slow as hell, especially the VNC part. Then I have my
enh dixit:
probably related to
https://code.google.com/p/android/issues/detail?id=66815. i think the
Right, similar issue.
hard part is what to set $TMPDIR to.
Agreed.
If I get a C API I can just call, I would put it into main.c in mksh
(set TMPDIR to that value, unless we import it from the
Lorenzo dixit:
The author says it's stronger than RC4, so (even if it hasn't been
significantly analyzed yet) it's more than good enough for mksh since $RANDOM
I’m currently of the mind to just not put any crypto code
into mksh, and just use the LCG unless the OS ships with
a very convenient
Dixi quod…
So, I’m most definitely n̲o̲t̲ looking for algorithms.
That being said, after having read
http://crypto.2014.rump.cr.yp.to/3de41b60e32a494c8f0fc9c21c67063a.pdf
and the first ten pages (up to beginning of chapter 4) of
http://people.csail.mit.edu/rivest/pubs/RS14.pdf
I’m impressed (the
Lorenzo dixit:
On 09/20/2014 07:14 PM, Thorsten Glaser wrote:
appears good enough for implementing it myself, and it may be
possible even to implement it in constant-time which is important
Hm, or maybe not. Also, the algorithm is extremely slow as is
already, and since MirBSD caters
Lorenzo dixit:
Wait, wait - 1. MirBSD?
Of course.
2. what did you measure exactly?
Nothing, I just saw the comparative measurements in the paper.
Are you considering RS14 for /dev/random?
Of course not. Just for both /dev/arandom and userspace arc4random().
Making a portable
Lorenzo dixit:
The real problem is that you can't count on getrandom() being there - eg it's
too new for my machine running debian sid... why they removed the sysctl()
without providing an alternative is beyond me instead.
Also, it’s Linux-specific, and not suitable for mksh anyway
since mksh
Dixi quod…
Its 1732 bit state beats the about 1700 bit of aRC4, too ;)
although that is due to the increase in registers.
And some of it is lost due to the CRUSH function, at least
OK. I slept over it, and I think that a Spritz-based
stretching RNG, to replace aRC4 in arc4random(), has
a bit
Ronald L. Rivest dixit:
There is no spritz mailing list or the like (yet); I'll let you know
if we create one.
We plan to publish an updated paper on Spritz within the next couple
of weeks on the IACR eprint site: http://eprint.iacr.org/
OK, thank you.
Keep an eye for this. The algorithm will
Ronald L. Rivest dixit:
I'm not sure why your proposed variation should produce
reduced loss of entropy?
CRUSH always reduces by 128 bit, but by changing the
amount of WHIP calls before a CRUSH, we shuffle things
around a bit more.
This matches the random skips we currently use in arc4random.
Tassilo Philipp | dyncall.org dixit:
Und es wird auch ne mksh gestartet von vim aus, mache ich von vim aus:
:!ps aux | grep sh
dann sehe ich mich auch richtig selber:
/usr/local/bin/mksh -c ps aux | grep sh
OK, da haben wir es: das ist keine interaktive Shell.
Mach ein -i vor das -c, falls
Dixi quod…
tl;dr: We probably should simplify the code (no promises
about $RANDOM other than its value area) and not export
$RANDOM any more, and only use arc4random-related functions
where really convenient, “lesser” OSes are SOL. We move
Later extensions (associative arrays) will require
My sincerest apologies to packagers/downstreams,
but I have found a regression in mksh today which made it necessary
to ship another release. I’m packaging it for several distros/OSes,
I know the pain.
We get two bugfixes:
unset x; nameref x ⇒ segfault (NULL pointer deref), except with glibc(‽)
Preliminary fix (as posted) committed and uploaded to Debian.
Better fix committed, needs more testing.
** Changed in: mksh
Status: Confirmed = In Progress
** Changed in: mksh
Assignee: (unassigned) = Thorsten Glaser (mirabilos)
--
You received this bug notification because you
: (unassigned) = Thorsten Glaser (mirabilos)
--
You received this bug notification because you are a member of mksh
Mailing List, which is subscribed to mksh.
Matching subscriptions: mkshlist-to-mksh-bugmail
https://bugs.launchpad.net/bugs/1381993
Title:
more fun with $*
Status in The MirBSD Korn
Tassilo Philipp | dyncall.org dixit:
So weit so gut - liege ich damit richtig, dass der Unterschied ist,
dass pdksh *immer* ENV reinzieht, aber mksh nur im interaktiven Modus?
Sorry für die späte Antwort – aber ich habe gerade Sourcen und
Historiën gelesen und alles, und festgestellt, daß dem in
Gerard Lally dixit:
OK my last question: I am lost! I am trying the following:
PS1 =
1) line break
2) reverse video, right-aligned $SHELL, $TERM, and $TTY, line break
This will not work without “bracketing” the ANSI codes in some
special character (see the manpage for this, the character is the
Gerard Lally dixit:
haha! Yes but it gives me an instant visual cue concerning path, user,
and host. Thank you again: that is service beyond the call of duty!
Nah. PS1 stuff is tricky, *and* it’s different from GNU bash, so I
officially offer a PS1 service ☺ especially to get converts.
You’re
Steffen Nurpmeso dixit:
11709 XSI On XSI-conformant systems, the
intptr_t and uintptr_t types are required; otherwise,
See. XSI is rare.
So if you go POSIX
I don’t. POSIX is still not ubiquitous. Also, POSIX is an
ever-changing standard.
use ssize_t with mksh
I
Hi all!
Thanks for this:
Commit ID: 100548597A713CD6746
CVSROOT: /cvs
Module name: src
Changes by:t...@herc.mirbsd.org2014/12/08 12:20:42 UTC
Modified files:
bin/mksh : Build.sh
Log message:
port this to GNU bash 1.12.1 from
Stephane Chazelas dixit:
[that's an email I sent to Thorsten a few weeks ago, reposting
here as I'm not sure it was delivered OK].
Yeah, sorry about that, I read it, and I planned to look at it
(thanks for the reproducers), but I haven’t gotten around doing
so due to lack of suitable hacking
enh dixit:
[ mksh testsuite ]
have you considered using sh instead? :-)
Not pure sh, that’s nowhere near enough. Maybe mksh. But if
the one just built has issues, that may mask it. If another,
you’ve got hen/egg problems.
Maybe C. But then, (cross-)building a C program to test another
one just
Stephane Chazelas dixit:
(with yesterday's git head and R46)
Hm, I changed some things wrt. unquoted $* to be more bash-like,
but… apparently, there is still loads to do.
Not that I'd expect anyone to use anything but [[ $* = ... ]].
Indeed.
(R46 gave a a there.)
Ah, that is probably the
Hi Debian bug, for completeness: mksh behaves similar to dash here,
both wrt. the “interesting” fd behaviour and the change fixing it.
Hi mksh mailing list, you might want to have a look at the bugreport
and what subsequently became known about fd redirection.
Michael Biebl dixit:
There I
Quoting your bugreport:
Package: mksh 46-2ubuntu3
Quoting the Debian bugreport of yours:
Found in version mksh/46-2
Fixed in version mksh/49-1
So, this is kinda to be expected, especially if *buntu lags behind like
this.
Anyway, I've put you an up-to-date build of mksh on my PPA:
Steffen Nurpmeso dixit:
I would prefer seeing a stack recursion limit exceeded or
similar before SIGSEGV happens because of recursive functions,
Yeah, but I have no idea how to do that. If you find one… tell me.
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
package.
Thanks!
The new changelog entries are:
mksh (50e-2ubuntu1) vivid; urgency=high
* Merge from Debian (LP: #1429469), remaining changes:
- Omit dietlibc builds on Ubuntu, where it is not in main
- Maintainer change for Ubuntu
-- Thorsten Glaser t.gla
, and the source
package.
Thanks!
The new changelog entries are:
mksh (50e-2ubuntu1) vivid; urgency=high
* Merge from Debian (LP: #1429469), remaining changes:
- Omit dietlibc builds on Ubuntu, where it is not in main
- Maintainer change for Ubuntu
-- Thorsten Glaser t.gla
Glaser t.gla...@tarent.de Sat, 07 Mar 2015 23:42:38
+
mksh (50e-2) experimental; urgency=medium
* QA upload.
* Backport upstream fix:
- [tg] SECURITY: make unset HISTFILE actually work
* Adjust shell version accordingly
-- Thorsten Glaser t...@mirbsd.de Sat, 07 Mar
it is not in main
- Maintainer change for Ubuntu
-- Thorsten Glaser t.gla...@tarent.de Sat, 07 Mar 2015 23:42:38
+
mksh (50e-2) experimental; urgency=medium
* QA upload.
* Backport upstream fix:
- [tg] SECURITY: make unset HISTFILE actually work
* Adjust shell
it is not in main
- Maintainer change for Ubuntu
-- Thorsten Glaser t.gla...@tarent.de Sat, 07 Mar 2015 23:42:38
+
mksh (50e-2) experimental; urgency=medium
* QA upload.
* Backport upstream fix:
- [tg] SECURITY: make unset HISTFILE actually work
* Adjust shell version accordingly
Glaser t.gla...@tarent.de Sat, 07 Mar 2015 23:42:38
+
mksh (50e-2) experimental; urgency=medium
* QA upload.
* Backport upstream fix:
- [tg] SECURITY: make unset HISTFILE actually work
* Adjust shell version accordingly
-- Thorsten Glaser t...@mirbsd.de Sat, 07 Mar
mksh R50e is out
** Changed in: mksh
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of mksh
Mailing List, which is subscribed to mksh.
Matching subscriptions: mkshlist-to-mksh-bugmail
https://bugs.launchpad.net/bugs/1381965
Title:
mksh R50e is out
** Changed in: mksh
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of mksh
Mailing List, which is subscribed to mksh.
Matching subscriptions: mkshlist-to-mksh-bugmail
https://bugs.launchpad.net/bugs/1381993
Title:
Hi everyone,
between coughing and sneezing I pushed out an upgrade of
the stable branch of mksh (plus a small new patch to fix
an infinite recursion problem), as I called for testing,
and nobody complained, what’s in CVS HEAD for a while.
So, enjoy R50e (mandatory bugfix upgrade with only a few
1 - 100 of 267 matches
Mail list logo
