[prev] [thread] [next] [lurker] [Date index for 2005/10/16]
* Abigail <abigail@xxxxxxx.xx> [2005-10-16 23:55]:
> > Can you throw in whitespace in those examples if you use the
> > new %hash??key?? syntax instead?
>
> Question marks? No idea to which syntax you are referring.
>
> > (And if not, would it at least be possible to parse the
> > examples umambiguously if it *were* allowed? If the answer to
> > that question is yes, then I would lobby for dropping the {}
> > hash lookup operator altogether and permitting whitespace
> > with the ???? operator.)
>
> I've heard about the ??:: operator, replacing the ?: one. But
> ????, no idea.
In both cases I am talking about the %hash<<key>> syntax (per
ASCII-transliterated version of the operator).
Bonus hate:
Software which does not cope with UTF-8, like your MUA, is
massively hateful.
But you're using a sufficiently recent mutt, so it is
configurable to cope. Adding `//TRANSLIT` to your $charset
should suffice to make to make a best-effort attempt to
transliterate undisplayable glyphs to something available in
your charset. No, I'm not sending UTF-8 out of flowery
notions, I actually need it. Yes, my MUA is configured
correctly.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>;
There's stuff above here
Generated at 20:00 on 17 Oct 2005 by mariachi 0.52