ALERT ALERT As pointed out by Damon Register in another post: if you are having weird problems and strange errors at boot, it appears that Kedit is doing an improper job of editing files. I have discovered many instances of comments stuck in the margins and lines wrapped incorrectly in files I have edited. It explains why I could not edit the idle time in wvdial.dod without it barfing, and pppd probs. All these files contained errors upon very close inspection. Excellent sleuthing, Damon. You've saved what's left of my hair! -- Tom Bishop tb64710@alltel.net RLU #12043 SuSE 7.1 PRO
This same phenomena happens when you install the updates for Apache. HTTPD.conf is corrupted by uncommented lines. An easy way to find the corrupted comments is to use Kdiff and compare the config.old with the new config file. This helps immensely with huge config files. also setting the column warp at 86 instead of 79 may help also. On Sunday 04 March 2001 23:23, you wrote:
ALERT ALERT
As pointed out by Damon Register in another post: if you are having weird problems and strange errors at boot, it appears that Kedit is doing an improper job of editing files. I have discovered many instances of comments stuck in the margins and lines wrapped incorrectly in files I have edited. It explains why I could not edit the idle time in wvdial.dod without it barfing, and pppd probs. All these files contained errors upon very close inspection. Excellent sleuthing, Damon. You've saved what's left of my hair!
-- Cheers, Jonathan
Hi, I've had this in the past with Kedit too - with firewall.rc.config, in fact. Sorry I didn't think of it as the reason folks had a problem. Kedit is still a nice little editor, though. But I suppose it would be good if you could customise its line lengths by methods more explicit than changing the font size, which does influence it's wrapping. For all I know, perhaps you can customize it, and thus have an 'easier on the head' editor than vi - though I'm starting to appreciate vi for all its oddities. So it's vi instead, this always works - though I would be grateful if anyone could spot a problem I have had with wanting a long line in firewall.rc.config, whether I use vi to enter it or not: I want a number of IP addresses in FW_TRUSTED_NETS, longer than fits on a line. So I broke the line with: FW_TRUSTED_NETS="lots of valid ipadresses going on in a line until i had to \ break the line and move onto another" because I thought that was the 'proper' way to escape a line break. But the ruleset absolutely will not load with this syntax. Shorten the line, remove the \ and all is peace and tranquility again. Clearly an egregious fluff on my part, but what am I doing wrong? Thanks all, Fergus On Monday 05 March 2001 05:23, you wrote:
ALERT ALERT
As pointed out by Damon Register in another post: if you are having weird problems and strange errors at boot, it appears that Kedit is doing an improper job of editing files. I have discovered many instances of comments stuck in the margins and lines wrapped incorrectly in files I have edited. It explains why I could not edit the idle time in wvdial.dod without it barfing, and pppd probs. All these files contained errors upon very close inspection. Excellent sleuthing, Damon. You've saved what's left of my hair!
I've found in the past that Kedit has caused me two problems, both fixed by correctly configuring the settings. First is the word wrap, causing the problems mentioned in this thread. The other is the changed owner/group, caused by having the back up option turned on. Since I turned off backup and word wrap, I have not had any more weird problems after editing a config file. Fergus Wilde wrote:
Hi,
I've had this in the past with Kedit too - with firewall.rc.config, in fact. Sorry I didn't think of it as the reason folks had a problem. Kedit is still a nice little editor, though. But I suppose it would be good if you could customise its line lengths by methods more explicit than changing the font size, which does influence it's wrapping. For all I know, perhaps you can customize it, and thus have an 'easier on the head' editor than vi - though I'm starting to appreciate vi for all its oddities.
So it's vi instead, this always works - though I would be grateful if anyone could spot a problem I have had with wanting a long line in firewall.rc.config, whether I use vi to enter it or not:
I want a number of IP addresses in FW_TRUSTED_NETS, longer than fits on a line. So I broke the line with:
FW_TRUSTED_NETS="lots of valid ipadresses going on in a line until i had to \ break the line and move onto another"
because I thought that was the 'proper' way to escape a line break. But the ruleset absolutely will not load with this syntax. Shorten the line, remove the \ and all is peace and tranquility again. Clearly an egregious fluff on my part, but what am I doing wrong?
Thanks all, Fergus
-- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://home.beseen.com/churches/joe_morris
mmmm.... I use Kedit exclusively and have never seen this problem.... ??? JLK On Sunday 04 March 2001 23:23, you wrote:
ALERT ALERT
As pointed out by Damon Register in another post: if you are having weird problems and strange errors at boot, it appears that Kedit is doing an improper job of editing files. I have discovered many instances of comments stuck in the margins and lines wrapped incorrectly in files I have edited. It explains why I could not edit the idle time in wvdial.dod without it barfing, and pppd probs. All these files contained errors upon very close inspection. Excellent sleuthing, Damon. You've saved what's left of my hair!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On March 5, 2001 01:23 am, Thomas Bishop wrote:
ALERT ALERT
As pointed out by Damon Register in another post: if you are having weird problems and strange errors at boot, it appears that Kedit is doing an improper job of editing files. I have discovered many instances of comments stuck in the margins and lines wrapped incorrectly in files I have edited. It explains why I could not edit the idle time in wvdial.dod without it barfing, and pppd probs. All these files contained errors upon very close inspection. Excellent sleuthing, Damon. You've saved what's left of my hair!
I've never used Kedit. I *highly* recommend using Kwrite instead. It's extremely configurable and does a good job of syntax highlighting. I move it's preference to the top for text files. Besides, more developers use it so bugs are often found and fixed quicker. - -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6o6uQHYysNB5h3fIRAt5vAKDPxUb5O7AiJ5yNPjBoF/LX2vRS0QCgqTqz oBhO1rRs+7nDvjsWvoNUqRw= =qCpu -----END PGP SIGNATURE-----
Quoting James Oakley on Mon, Mar 05, 2001 at 11:06:56AM -0400:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On March 5, 2001 01:23 am, Thomas Bishop wrote:
ALERT ALERT
As pointed out by Damon Register in another post: if you are having weird problems and strange errors at boot, it appears that Kedit is doing an improper job of editing files. I have discovered many instances of comments stuck in the margins and lines wrapped incorrectly in files I have edited. It explains why I could not edit the idle time in wvdial.dod without it barfing, and pppd probs. All these files contained errors upon very close inspection. Excellent sleuthing, Damon. You've saved what's left of my hair!
I've never used Kedit. I *highly* recommend using Kwrite instead. It's extremely configurable and does a good job of syntax highlighting. I move it's preference to the top for text files.
Besides, more developers use it so bugs are often found and fixed quicker.
- -- Vim. Never had it do unusual things to a script or configuration file a single time :) Or perhaps joe :)
-- Michael Perry mperry@tsoft.com ------------------
participants (7)
-
Fergus Wilde -
James Oakley -
Jerry Kreps -
Joe Morris -
Jonathan Drews -
Michael Perry -
Thomas Bishop