[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13177: 24.3.50; doc of `read-char-by-name'
From: |
Drew Adams |
Subject: |
bug#13177: 24.3.50; doc of `read-char-by-name' |
Date: |
Sat, 15 Dec 2012 08:08:08 -0800 |
> >> Dunno just what the intention was for this function. If it really
> >> was to return a recognized Unicode character then this is a product
> >> bug and reading should not end until the user enters matching input
> >> (or hits `C-g').
>
> > As its docstring says, it also accepts a hexadecimal number
> > of Unicode code whose input can't use completion.
>
> That does not preclude using require-match.
Yes.
The problem for me is that I don't know what the intention (design) was or why.
Maybe someone has a good reason to return nil or to return a number that does
not correspond to a recognized code point?
The design should be clarified (and perhaps decided/changed, if appropriate)
before we try to fit the doc to it.
- bug#13177: 24.3.50; doc of `read-char-by-name', Drew Adams, 2012/12/13
- bug#13177: 24.3.50; doc of `read-char-by-name', Juri Linkov, 2012/12/15
- bug#13177: 24.3.50; doc of `read-char-by-name', Stefan Monnier, 2012/12/15
- bug#13177: 24.3.50; doc of `read-char-by-name',
Drew Adams <=
- bug#13177: 24.3.50; doc of `read-char-by-name', Stefan Monnier, 2012/12/15
- bug#13177: 24.3.50; doc of `read-char-by-name', Drew Adams, 2012/12/15
- bug#13177: 24.3.50; doc of `read-char-by-name', Juri Linkov, 2012/12/16
- bug#13177: 24.3.50; doc of `read-char-by-name', Andreas Schwab, 2012/12/16
- bug#13177: 24.3.50; doc of `read-char-by-name', Juri Linkov, 2012/12/16
- bug#13177: 24.3.50; doc of `read-char-by-name', Drew Adams, 2012/12/16
- bug#13177: 24.3.50; doc of `read-char-by-name', Drew Adams, 2012/12/16
- bug#13177: 24.3.50; doc of `read-char-by-name', Chong Yidong, 2012/12/21
- bug#13177: 24.3.50; doc of `read-char-by-name', Drew Adams, 2012/12/21
bug#13177: 24.3.50; doc of `read-char-by-name', Drew Adams, 2012/12/15