On Sat, Jun 14, 2008 at 07:04:53PM +0200, Werner LEMBERG wrote:
> If you don't agree with these mappings, you could use the .tr request
> to change that, for example
>
> .tr `'
>
> so that `foo' in input becomes 'foo' in output. Alternatively, you
> might use the .char request like this:
>
>
> Yeah, I think that's what's needed. Debian does tr \[oq] ' (only)
> and I'm not sure if that's also be needed. For latin1, it might be
> nicer to keep ` as it is, and instead map ' and \[cq] to an acute
> accent.
Well, since it is often the case that man pages cite shell input code
like
$ g
Hi Werner,
> > Yeah, I think that's what's needed. Debian does tr \[oq] ' (only)
> > and I'm not sure if that's also be needed. For latin1, it might be
> > nicer to keep ` as it is, and instead map ' and \[cq] to an acute
> > accent.
>
> Well, since it is often the case that man pages cite she
On Sun, Jun 15, 2008 at 02:39:03PM +0200, Werner LEMBERG wrote:
> Well, since it is often the case that man pages cite shell input code
> like
>
> $ grep foo `find -name 'xxx.*'`
>
> it is quite important IMHO to have proper cut and paste from a man
> page displayed in a terminal. With other w
On Sun, Jun 15, 2008 at 03:06:35PM +0100, Ralph Corderoy wrote:
> It's horrible for an author to have to use character escapes instead of
> the glyphs readily available on the keyboard for normal text; it
> interrupts the flow of typing. Surely the solution should allow the
> `normal' entry of qu
> Since any code extracts, C, shell, etc., often already need
> manipulation, perhaps because they contain the escape character,
> it's these that should use \` and \', e.g.
OK.
> That just leaves getting grotty to output ' for ` if \*(.T is ascii
> by doing .tr `' as you suggested. As Stuart sa
> > With other words: Within normal text, it's probably best to use
> > \[oq] and \[cq], and within verbatim code fragments, plain ' and `
> > should be used as-is.
>
> Huh? Sorry, but isn't that what \` and \(aq are for?
Sorry, my mistake.
Werner
