User forums > Nightly builds
The 18 February 2008 build (4893) is out.
rhf:
--- Quote from: killerbot on February 27, 2008, 05:22:36 pm ---ah, that one is placing those "...", but bookmarks ??
--- End quote ---
BrowseTracker is one of my favorite plugins, and I am very glad that it has been added to the contributed plugins list.
However, I have seen several questions about the "..." . Perhaps it would be preferable to have its Browse_Marks/Book_Marks turned off or hidden by default.
Pecan:
--- Quote from: rhf on February 27, 2008, 05:50:23 pm ---
--- Quote from: killerbot on February 27, 2008, 05:22:36 pm ---ah, that one is placing those "...", but bookmarks ??
--- End quote ---
BrowseTracker is one of my favorite plugins, and I am very glad that it has been added to the contributed plugins list.
However, I have seen several questions about the "..." . Perhaps it would be preferable to have its Browse_Marks/Book_Marks turned off or hidden by default.
--- End quote ---
Done. Svn 4916.
But it means current users of Browse Marks must now go enable BrowseMarks in the settings dialog.
rhf:
--- Quote from: Pecan on February 27, 2008, 08:29:32 pm ---
--- Quote from: rhf on February 27, 2008, 05:50:23 pm ---BrowseTracker ... . Perhaps it would be preferable to have its Browse_Marks/Book_Marks turned off or hidden by default.
--- End quote ---
Done. Svn 4916.
But it means current users of Browse Marks must now go enable BrowseMarks in the settings dialog.
--- End quote ---
Pecan,
I updated and built SVN 4916 and the contributed plugins. Based on a couple of quick tests, it appears your BrowseTracker changes work as expected (on Windows XP).
stevenkaras:
--- Quote from: bttr on February 26, 2008, 10:42:16 pm ---Bug: $file_ext resolves to file extension + " sign. :(
--- End quote ---
I've seen this bug pop up with some batch scripts I wrote a while back. It happened when I took the scripts I had written, and copied them to another computer. Of course, I assumed they would work. They didn't.
As it turns out, the code that windows uses to generate a file name and pass it along to a program is fairly complex, and varies with the version of windows(which as you may not know, is not the same as the edition). In general:
1. if the file path contains spaces, the path is put inside quotes
2. if the file path doesn't contain spaces, the behavior is undefined(just like what a c++ compiler does for any number of ambiguous statements: i++ / 2 - ++i * 5)
From what I've seen, non-english windows tends to enclose filepaths in quotes more often than not. As for why you see it as a single quote at the end of a make variable, seems to me that the parsing for that variable needs a bit more error-checking. Took me 2 days to figure out what was going on with those batch scripts...
Paco.Blasco:
The version for MAC is not working with Spanish keyboards. I suppose also that it doesn't work over non-English keyboards. We can not have access to "[" or "{".
Also, I suppose the problem is in Scintilla.
Any idea?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version