Unrelated Motif annoyance

[Fergal Mullally]

While we're talking about Motif et al., I have a minor annoyance with
Nedit running on Ubuntu 8.04LTS, that I think is Motif related.

When I start nedit from the command line and then open an "Open File"
dialog, a whole bunch of debugging information squirts out onto my
xterm window


Name: FilterText
Class: XmTextField
Character '\57' not supported in font. Discarded.


Name: FilterText
Class: XmTextField
Character '\150' not supported in font. Discarded.


Name: FilterText
Class: XmTextField
Character '\157' not supported in font. Discarded.
(and so forth)



The problem always happens the first time I open the dialog, but
intermittantly afterwards. The program doesn't crash, but the
behaviour is annoying, and I'm wondering if there's some kind of easy
fix.


I think I'm using a binary I downloaded from the website. Here's the
version info:

NEdit 5.5
Sep 30, 2004

Built on: Linux, 486, GNU C
Built at: Aug 17 2006, 21:44:42
With Motif: 2.2.3 [@(#)Motif Version 2.2.3] (UNTESTED)
Running Motif: 2.2 [unknown]
Server: The X.Org Foundation 10400090
Visual: 32-bit TrueColor (ID 0x23)
Locale: en_AU.UTF-8




Any help'd be appreciated.

Fergal

[Joerg Fischer]

Post by Fergal Mullally
Name: FilterText
Class: XmTextField
Character '\57' not supported in font. Discarded.
[...]
NEdit 5.5
Sep 30, 2004
Built on: Linux, 486, GNU C
Built at: Aug 17 2006, 21:44:42
Running Motif: 2.2 [unknown]
Server: The X.Org Foundation 10400090
Visual: 32-bit TrueColor (ID 0x23)
Locale: en_AU.UTF-8

NEdit doesn't support UTF-8. This also means, you can't open files
with file names encoded in UTF-8 (containing characters outside 7bit
ASCII). I think the messages just tell you some UTF-8 encoded
characters are tried to be displayed in the open dialog, which won't
work. (One of the first things I do with any Linux installation is
to stop Unicode mode, since I just don't need it.)

--Jörg

[Offer Kaye]

Post by Fergal Mullally
When I start nedit from the command line and then open an "Open File"
dialog, a whole bunch of debugging information squirts out onto my
xterm window

I had a similar problem, not the same messages but the same idea -
lots of debugging messages spewed onto the xterm window.
I just suppressed them by redirecting the nedit command STDOUT/ERR to
/dev/null. So for example in tcsh I use:

nedit some_file >& /dev/null

Bash redirect syntax is slightly different, look it up in "man bash"
if that's your shell.

Cheers,