From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: printf %s in UTF-8 is not POSIX-compliant
Date: Thu, 06 Mar 2008 18:29:44 -0800 [thread overview]
Message-ID: <080306182944.ZM22141@torch.brasslantern.com> (raw)
In-Reply-To: <20080306174523.15633059@news01>
On Mar 6, 5:45pm, Peter Stephenson wrote:
} Subject: Re: printf %s in UTF-8 is not POSIX-compliant
}
} On Thu, 06 Mar 2008 09:09:01 -0800
} Bart Schaefer <schaefer@brasslantern.com> wrote:
} > However, if "emulate bash" is going to mean something other than a
} > synonym for "sh", then some effort should be put into being a bit
} > closer to bash than it's currently possible to be. For example,
} > at least set the various BASH_* options, the way "emulate csh" sets
} > the smattering of CSH_* options.
}
} I'm not sure the first sentence agrees with the second. Are you
} suggesting new options?
Well, I considered suggesting that we comprehend bash prompt sequences,
but then decided that was going too far. What I meant, I guess, was
"closer than it's currently possible to get by running 'emulate'".
} > A final thought on MULTIBYTE: Is it perhaps reasonable to split this
} > into two options, one that affects line editor operations and one that
} > affects internals?
}
} I think it can be done, and is reasonable if done properly, but is
} likely to be bug-prone in the case where one option is on and the
} other off.
Yes, that's exactly the issue. Regardless of the size or complexity of
the job to alter the C code, it's unreasonable if the result introduces
more script bugs than it fixes incompatibilities.
prev parent reply other threads:[~2008-03-07 2:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 1:29 Vincent Lefevre
2008-03-04 1:37 ` Vincent Lefevre
2008-03-04 9:40 ` Peter Stephenson
2008-03-05 0:27 ` Vincent Lefevre
2008-03-05 1:34 ` Bart Schaefer
2008-03-06 1:27 ` Vincent Lefevre
2008-03-05 10:41 ` Peter Stephenson
2008-03-06 1:39 ` Vincent Lefevre
2008-03-06 9:46 ` Peter Stephenson
2008-03-06 17:09 ` Bart Schaefer
2008-03-06 17:45 ` Peter Stephenson
2008-03-07 2:29 ` Bart Schaefer [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=080306182944.ZM22141@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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 public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).