Your message dated Thu, 13 Apr 2006 11:23:07 -0400
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #361177,
regarding vim-common: Please allow posix/sus shell syntax, without other
extensions
to be marked as having been forwarded to the upstream software
author(s) Charles E Campbell Jr <[EMAIL PROTECTED]>.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Chip,
Following up with the previous sh.vim reports, the user has filed a
wishlist bug for an is_posix (my wording) feature to sh.vim. Included
below is his full request. Would you mind taking a look and letting me
know if you'd consider adding such a feature?
Thanks,
James
On Thu, Apr 06, 2006 at 10:48:24PM -0400, Justin Pryzby wrote:
> I would like to be able to write, for example, a Debian maintainer
> script, and I would like to use #! /bin/sh to allow people to use
> whatever shell they want, rather than adding an additional dependency
> on some specific shell. Anything installed as /bin/sh is guaranteed
> to support all the posix stuff (whether this is an old posix or new
> SUS isn't defined); (it is also guaranteed to support echo -n).
>
> bash is Essential: yes, so I could write everything with #!/bin/bash,
> but some find bash to be slow, big, or want to be able to share code
> to systems that don't have bash (but where /bin/sh is posix). So I
> would like to write a posix shell script, using #!/bin/sh. vim
> doesn't presently support this well; I either have to allow all syntax
> allowed by some specific shell like bash, including some stuff which
> will break with a strict posix shell, or I have to use #! /bin/sh, and
> deal with vim marking lots of stuff as invalid which is perfectly
> valid in this context.
signature.asc
Description: Digital signature
--- End Message ---
