[John Cordes]

AHA—I hadn’t looked at Display before; as you can see I am a complete novice with syntax files. Thank you, that solves the issue for me.

[John Cordes]

Thanks! I have realized that my problem is that I was in ‘dark mode’ and the green (for comment lines) was so faint (against the dark background) it did not look to be coloured at all. My eyesight is not very good and I could hardly read the comments, which is why I wanted a colour for them which would stand out better.
I switched to ‘light mode’ and can now see that the comments are, just barely, in a green colour.
Can you please tell me how I could assign a different colour to the comments?

Thanks,
John

[John Cordes]

Thanks.
I have been trying to modify the bash.esy syntax file to highlight comment lines. I tried this modification (adding the last entry “^#”):
#Keyword color=4,word=on,rightall=off,case=off,insidetag=off,regexp=off
&&
&
||
|
^#

as a test, but after importing the new file there is still no highlighting of the bash comment lines such as
# functions

Is there something I’m missing?

Thanks,
John Cordes

[John Cordes]

Thank you! I had just run into the same problem—not understanding why the Import button was greyed out. I appreciate your detailed explanation.
John C.

[John Cordes]

Thanks – I have submitted a zipped file. I presume it does contain embedded newlines but I am unclear just what to do about that.

[John Cordes]

Hello Yutaka,
Thank you for the quick update. I have installed 18.0.7 and tried it on a couple of the CSV files I described.
I find myself somewhat puzzled by the results.
First, when I load the smaller test file I mentioned, I do see 109 lines in both modes (csv and normal), no matter whether the “Allow newlines in double quotes” box is cleared or not.
However, when I open the complete file (before I began deleting lines to try to get to a simple test file situation), things are more complicated.
With the ‘newlines’ box cleared, I find the same results in both csv and normal mode: 10,284 lines. There are just 2 lines in the Output window (in csv mode):
(2036): Invalid double quotes.
(2036): Inconsistent number of columns detected.

With the ‘newlines’ box checked, I see 10,284 lines in normal mode (expected result I think) but only 7,883 lines in csv mode. In csv mode for this case the Output window contains these lines:
(2036): Invalid double quotes.
(2036): Inconsistent number of columns detected.
(2082): Invalid double quotes.
(2085): Invalid double quotes.
(2160): Invalid double quotes.
(2170): Invalid double quotes.
(2303): Invalid double quotes.
(2765): Invalid double quotes.

My reduced test file is 203 KB in size, the original file is 2.88 MB. I would be prepared to send either file to you if you would like to check them out yourself.

[John Cordes]

Brief follow-up: I have just tried your suggestion of clearing the “Allow newlines in double quotes” check box in the CSV page of the Customize dialog box. That did indeed make my test file display properly. I believe it is working properly for my original source file also but should check some details to be certain. It also made the display in csv mode *much* faster. Thank you for this suggestion. I’m not sure that I understand just what is happening though — have not been able to spend much time on this today.

[John Cordes]

Hello Yutaka,
Thank you for the prompt response. I am glad to hear that the issue is understood and will soon be corrected. I would send you my reduced file, but it still contains data involving other people which should probably be kept private. Even though I have pared it down a lot from the original, it is not easy to work with (mostly because of the large number of columns still present), so is difficult to ‘clean’. I would be glad to try out a new test version, if you would care to send it to me when ready. I am not sure if the source file contains embedded newlines but will look into that later.

[Author]

Posts