🚀 go-pugleaf

I am using fonts with printable characters in the range 0200..0237.  With
epoch4.2, I have to set ctl-arrow to neither nor t to be able to see them
as characters rather than \xxx.  But then, epoch4.2 line positionning gets
confused. If you have such a character on a line, then you cannot reach
the remaining of the line with mouse pointing and text-cursor rarely
appears in it.  Playing with it makes epoch quickly coredump.

I think it's a bad idea to make the hypothesis that characters in the
range 0200..0237 are not printable.  We already have had enough astute
hypotheses in emacs (7bits display, 7bits keymaps) not to settle a new
one.  I do believe in homogeneity.  Unless someone can think of a text
file where one could have both 0200..0237 and 240..0377 characters, not
wanting to see them either both as printable characters or both as octal.
I already mentionned this problem for Lucid Emacs.  People interessed
might take a look at the newsgroup alt.lucid-emacs.bug (subject: 8bits
display) for comments/propositions.

If you want to use the package "viewer" safely (see message "Some tools
available" dated 18 Aug 92 17:02:59 GMT), then you'll have to change
buffer.h to define:
#define is_meta_char(c) ((c) >= 0200 && (c) <= 0377)

BTW, 0240 is considered as meta everywhere (doc, cmds.c, ...) except in
is_meta_char. Test should be "(c) >= 0240" rather than "(c) > 0240".

Renaud

PS (for Marc):  0200..0237 make 8 bits characters blink :-)