all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: user@abyayala.i-did-not-set--mail-host-address--so-tickle-me
To: mbakke@fastmail.com
Cc: 26984@debbugs.gnu.org
Subject: bug#26984: closed (Re: bug#26984: Add loksh (ported OpenBSD pdksh))
Date: Sat, 20 May 2017 09:19:32 +0000	[thread overview]
Message-ID: <87shjzc2cb.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <handler.26984.D26984.149524097422781.notifdone@debbugs.gnu.org> (GNU bug Tracking System's message of "Sat, 20 May 2017 00:43:02 +0000")

help-debbugs@gnu.org (GNU bug Tracking System) writes:

> ng0 <ng0@pragmatique.xyz> writes:
>
>> Subject: [PATCH] gnu: Add loksh.
>>
>> * gnu/packages/shells.scm (loksh): New variable.
>
> Thanks for this patch! I've used this shell a lot on OpenBSD. One
> thing it does better than bash is that ^W stops at "/" and other
> boundaries, not just spaces!
>
> I've applied it with a slight adjustment to description:

>> By the way, this can not be used for the test suite in graphviz.
>> There are many ksh implementations, and this is not the one
>> the tests accept. Or at least its ksh93 checks fail ;)
>
> Maybe they need "mksh"? Another popular Korn Shell :)

Maybe. It must be a ksh93 implementation, most implementations
are ksh88. I don't know enough about ksh to know if a shell
is compatible. I executed ksh and ran the lines which test for
ksh88 or ksh93. It failed.

      parent reply	other threads:[~2017-05-20 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 18:20 bug#26984: Add loksh (ported OpenBSD pdksh) ng0
2017-05-18 20:22 ` ng0
2017-05-20  0:42   ` Marius Bakke
     [not found] ` <handler.26984.D26984.149524097422781.notifdone@debbugs.gnu.org>
2017-05-20  9:19   ` user [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87shjzc2cb.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me \
    --to=user@abyayala.i-did-not-set--mail-host-address--so-tickle-me \
    --cc=26984@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.