The line that made my night!

[pseydtonne]

alias typing='nedit -xrm "nedit*text.background: darkblue" -xrm "nedit*text.foreground: yellow"'

The above is not perfect (I'd prefer Prussian blue and maybe a sea foam green for the text), but it does convey what I want the text editor nedit to do when I use it for writing LiveJournal entries. I didn't have to dig all that long through the manuals. All I had to do was start myself over.

First, I typed "man nedit" and found out about the flag that overrides X defaults (-xrm) and the format it likes. This flag either has an obscure concatenation character or it just doesn't perform more than one tweak each time it's invoked. Then I made an alias for this string of crud so that I could get my desired colors each time I call up the program and added the string into my .bashrc file.

I also added this line to my .bashrc because my mod for my virtual consoles (which I'd added to my .bash_profile) wasn't getting called to my X terminals:

PS1="\@. \u is in \W\$ "

This way, I get the time, who I'm logged in as and the last directory I'm in each time I hit enter.

Yeeeeeee! Now all I need is some time to read the documentation I just found for the Grand Unified Bootloader and I'll be sound as a pound.

By the way, I had a fine day on the sales floor and I'm almost ready for bed.

-geek pride all the way, Dante

Comments

[pseydtonne.livejournal.com]

There is, but it "should not be edited by the user". It seems to be read-only -- nedit can write to the .neditrc but whatever you write to it will be ignored. You can change settings within nedit and save those, but it acts very strange about which settings you'd want to save (typeface is fine, but color isn't). This starts sounding more and more like MicroSoft software, doesn't it?

Lazy programming, I say. "Oh, leave it to the windowing manager." Why? I only want this in the app, not all windows.