Discuss Digest, Vol 62, Issue 10

[Fergal Mullally]

Thanks for your suggestions. Aliasing nedit to 'nedit &> /dev/null'
(in bash) sounds like the easier solution.


Fergal

Send Discuss mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
       http://www.nedit.org/mailman/listinfo/discuss
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss digest..."
  1. Re: Unrelated Motif annoyance (Joerg Fischer)
  2. Re: Unrelated Motif annoyance (Offer Kaye)
----------------------------------------------------------------------
Message: 1
Date: Mon, 9 Mar 2009 12:18:09 +0100
Subject: Re: Unrelated Motif annoyance
Content-Type: text/plain; charset=ISO-8859-1

    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
------------------------------
Message: 2
Date: Mon, 9 Mar 2009 13:25:08 +0200
Subject: Re: Unrelated Motif annoyance
Content-Type: text/plain; charset=ISO-8859-1

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
nedit some_file >& /dev/null
Bash redirect syntax is slightly different, look it up in "man bash"
if that's your shell.
Cheers,
--
Offer Kaye
------------------------------
_______________________________________________
Discuss mailing list
http://www.nedit.org/mailman/listinfo/discuss
End of Discuss Digest, Vol 62, Issue 10
***************************************