Blanks at end of lines

[c24m48]

Versions previous to V9 had an option to get rid of blanks at the end of lines. The option was controlled by a check box in the Editor 2 tab of the Editor options. I can't find the option in V9. Could you point me to it?

The option seem to affect both the content of saved files, and also the behavior of the keyboard END key, which I use rather a lot. I would like to specify an option so that the END key will go to the end of the last non-blank character. As I said, V8 had such an option and I am unable to find the option in V9.

In general, the Editor 2 tab of the Editor options has many fewer options in V9 than it did in V8. I haven't studied the two lists in detail to see what's missing in V9. In addition to the blank at end of line option, is there some other place to find the other V8 options from the Editor 2 tab in V9?

[Albert Wiersch]

Versions previous to V9 had an option to get rid of blanks at the end of lines. The option was controlled by a check box in the Editor 2 tab of the Editor options. I can't find the option in V9. Could you point me to it?

CSE HTML Validator v9.0 uses a new editor component. It doesn't have the option to automatically remove all the blanks at the end of all the lines when you open a document. Also, some of the options supported in v8 are not supported with the new editor component, but I don't think these options are often used.

Would the ability to remove the blanks at the ends of the selected lines be helpful? You could then do this manually for only the lines you wanted to. You could do it for the entire document by selecting all the lines with Ctrl+A then choosing the option to remove ending whitespace. Then the 'End' key should work as you want.

[c24m48]

If such an option existed, I would probably use it. So yes, it would be helpful. However, I'm finding that every time I open a file, many of the lines in the file seem to be acquiring trailing white space that I know for a fact wasn't there before and that I know for a fact I didn't put there. Where is the trailing white space coming from? What I really want is restoration of the V8 option where that white space isn't there in the first place.

In all candor I regret to say that I am disappointed in the new editor component of V9. I've been an extremely satisfied user and customer of CSE HTML Validator for many years. V9 is the first release that has disappointed me. In particular, I find myself constantly fighting with the new editor component in minor but irritating ways. There's nothing that keeps me from getting my work done, but it sure is frustrating. I'm not sure I can easily catalog all the irritations. The trailing white space issue is just one of several. Therefore, I end up going back to use V8 on a regular basis.

[Albert Wiersch]

If such an option existed, I would probably use it. So yes, it would be helpful. However, I'm finding that every time I open a file, many of the lines in the file seem to be acquiring trailing white space that I know for a fact wasn't there before and that I know for a fact I didn't put there. Where is the trailing white space coming from? What I really want is restoration of the V8 option where that white space isn't there in the first place.

I do not know where the white space is coming from. The editor should not be adding it by itself. If you can replicate a situation where the editor is adding white space, then I'd really like to know so I can replicate it here and get it fixed.

I will also work on getting that option added.

In all candor I regret to say that I am disappointed in the new editor component of V9. I've been an extremely satisfied user and customer of CSE HTML Validator for many years. V9 is the first release that has disappointed me. In particular, I find myself constantly fighting with the new editor component in minor but irritating ways. There's nothing that keeps me from getting my work done, but it sure is frustrating. I'm not sure I can easily catalog all the irritations. The trailing white space issue is just one of several. Therefore, I end up going back to use V8 on a regular basis.

Sorry you are disappointed. The new editor component was necessary to move forward as it supports Unicode and many other important features that were not previously supported.

If you could let me know what these irritations are, then I can try to address them. Please base them on the latest BETA though, and not v9.01.

[Albert Wiersch]

OK, I've added an option to remove the trailing whitespace from the selected lines. It will be in the next version.

However, I'd still like to know where that trailing whitespace is coming from because CSE HTML Validator shouldn't be adding it by itself.

[c24m48]

Thanks for looking into this. I apologize that I haven't gotten back to you with a scenario to recreate the trailing space problem. I promise to do that as soon as I get a few minutes.

In the meantime, I have a question and two comments. The question has to do with the forthcoming option to remove the trailing whitespace from the *selected* lines. What does that mean exactly? Previous to V9, there was an option that would automatically remove trailing whitespace from *all* lines at the time the file was saved. Once I turned the option on, I never had to think about it again and I never had to think about selecting lines. Is that the way the forthcoming option for V9 is going to work, or do you have to select the lines for which you want the trailing white space removed?

The first comment has to do with what appears to be a little glitch in the V9 editor. Suppose the cursor is at the end of a line and that the next line exists but is empty. A down arrow followed by an up arrow does not restore the cursor to where it was. Which is to say, the cursor is no longer at the end of the line. Rather, it has moved one character to the left of the end of the line. Previous to V9, the same scenario would return the cursor to the end of the line. There are other similar glitches in cursor movement, but this one is easy to describe and it happens to me all the time.

The second comment has to do with Find, repeat Find with F3, and a bolding operation. Many of my Web pages have to do with genealogy, and a common genealogical convention is to render people's last names in a bold font. So I will do something like do a Find for Smith, do a CTL-B to bold the name, F3, CTL-B, F3, CTL-B, etc. Of course, I make sure CTL-B uses the *strong* tag rather than the *b* tag. This works fine previous to V9, but in V9 you have to hit F3 twice because the bolding operation doesn't seem to leave the cursor in the correct place.

I should explain that you really can't do this operation with a global replace. You really have to look at each instance of the last name before you bold it. For example, the last name may sometimes appear in a plural or possessive form. The last name may appear in a place in the file where bolding is not permitted by HTML rules. The last name may appear as a part of a place name that should not be bolded, e.g., the Smith family may have lived in Smith County or in the town of Smithville. Last names can also be first names. And lots of etc. The operation really requires human intelligence and really needs the F3 CTL-B sequence rather than a global replace.

[Albert Wiersch]

Thanks for looking into this. I apologize that I haven't gotten back to you with a scenario to recreate the trailing space problem. I promise to do that as soon as I get a few minutes.

Hello,

Thanks for getting back to me. I will reply to this message in detail next week as I'm currently taking some vacation time.

[Albert Wiersch]

Thanks for looking into this. I apologize that I haven't gotten back to you with a scenario to recreate the trailing space problem. I promise to do that as soon as I get a few minutes.

Thanks, that would be helpful.

In the meantime, I have a question and two comments. The question has to do with the forthcoming option to remove the trailing whitespace from the *selected* lines. What does that mean exactly? Previous to V9, there was an option that would automatically remove trailing whitespace from *all* lines at the time the file was saved. Once I turned the option on, I never had to think about it again and I never had to think about selecting lines. Is that the way the forthcoming option for V9 is going to work, or do you have to select the lines for which you want the trailing white space removed?

You will have to manually select the lines (or the entire document with Ctrl+A), then choose the option. I do not think the program should be automatically removing or changing any documents because it might not be what is wanted.

The first comment has to do with what appears to be a little glitch in the V9 editor. Suppose the cursor is at the end of a line and that the next line exists but is empty. A down arrow followed by an up arrow does not restore the cursor to where it was. Which is to say, the cursor is no longer at the end of the line. Rather, it has moved one character to the left of the end of the line. Previous to V9, the same scenario would return the cursor to the end of the line. There are other similar glitches in cursor movement, but this one is easy to describe and it happens to me all the time.

Thanks. I reproduced this with an older version of the editor component but the newer version which will be in v9.02 seems to resolve this issue.

The second comment has to do with Find, repeat Find with F3, and a bolding operation. Many of my Web pages have to do with genealogy, and a common genealogical convention is to render people's last names in a bold font. So I will do something like do a Find for Smith, do a CTL-B to bold the name, F3, CTL-B, F3, CTL-B, etc. Of course, I make sure CTL-B uses the *strong* tag rather than the *b* tag. This works fine previous to V9, but in V9 you have to hit F3 twice because the bolding operation doesn't seem to leave the cursor in the correct place.

Thanks. I think I know what you're saying and will try to address this in a future update.

I should explain that you really can't do this operation with a global replace.

Yep, things are usually not as simple as they first seem! This brings to mind the saying that "the devil is in the details."

[Albert Wiersch]

Thanks. I think I know what you're saying and will try to address this in a future update.

This should now be fixed in the next update.