For the first time since may i've NOT updated my x5 to bleeding edge every day (was partying in denmark during weekend instead) and i was running cvs: 060920-2007... Now i'm running 060925-1955 - and i'm delighted by your way of thinking and organizing menues - thank you.

However, this option does not appear in my Tag Cache menu. Thinking it might be smart enough to display only if the 'custom' menu exists, I created the following simple tagnavi_custom.config file (using Notepad, saving as UTF-8) from roolku's example above:

Still no joy. I just cannot get a custom menu to display at all. I've modified previous versions of tagnavi.config without problems, so I don't think it's a file format issue. I have also modified the new default tagnavi.config and can see the changes I've made having an effect on the menu.

I just tried your example. Works for me, but:when saving the file as utf-8 with BOM it doesn't work. You need to make sure to save without a BOM. Apart from that, as long as your file doesn't include characters outside of the ASCII set utf-8 is identical to ASCII, so there's no need to save it as utf-8. (Edit: the lower 127 characters of ASCII that is.)

Just remove the BOM, that worked fine for me. Notepad is really ugly when it comes to utf-8 files. I suggest using a different editor which can handle utf-8 better (I used vim and Crimson Editor).

I took that option off roolku's file, because, AFAICT, that option completely replaces the default Tag Cache menu with the custom one. ATM all I am trying to do is add a custom menu to the existing list. Once I get that working I'll branch out into more esoteric stuff. I'm just frustrated that it doesn't seem to work as simply as it appears it should do.

I just tried your example. Works for me, but:when saving the file as utf-8 with BOM it doesn't work. You need to make sure to save without a BOM. Apart from that, as long as your file doesn't include characters outside of the ASCII set utf-8 is identical to ASCII, so there's no need to save it as utf-8. (Edit: the lower 127 characters of ASCII that is.)

Just remove the BOM, that worked fine for me. Notepad is really ugly when it comes to utf-8 files. I suggest using a different editor which can handle utf-8 better (I used vim and Crimson Editor).

So, using the magic of Wikipedia, I now know what BOM is, but not yet how to remove it Â Is there an easy way to do this?

I am also aware that Notepad is not the best text editor out there, but my previous dabblings in this area have always worked OK, so I made the assumption that it would be OK this time. I'll try Notepad++ or Notepad2. EDIT: Well I got it working by copying my config text into a copy of the default config file and re-saving it. I presume I got the BOM issue by copying and pasting from the forum into a new Notepad file? Not something I've come across before, but hey, you need to learn something new every day...

@ roolku - your config rocks!

As for the UTF-8, I used that because I thought, (probably incorrectly) that it fixed the LF/CR vs LF-only issue.

To remove the BOM you need to get a decent editor. In my case, I used Crimson Editor in which I can change the document encoding (Document / Encoding Type / UTF-8 w/o BOM). Of course you can also use a hex-editor and delete the first three bytes ;-) The problem is (afaik) that windows notepad simply always adds a BOM if a file is saved as utf-8. But if you don't need utf-8 you can simply save files as ASCII (which also works with notepad).The CR/LF issue is something completely different.

To remove the BOM you need to get a decent editor. In my case, I used Crimson Editor in which I can change the document encoding (Document / Encoding Type / UTF-8 w/o BOM). Of course you can also use a hex-editor and delete the first three bytes ;-) The problem is (afaik) that windows notepad simply always adds a BOM if a file is saved as utf-8. But if you don't need utf-8 you can simply save files as ASCII (which also works with notepad).The CR/LF issue is something completely different.

Our posts crossed in the ether and you can see I have managed to get it working now, but thanks for those explanations, you have been very helpful