Hi Karl, > @2008-01-18 18:56 -0600: > Just FYI, in practice, what I recall past versions of Emacs (that is, > next-error) doing is, more or less, looking for /^(.*):[0-9]: / and then > the filename is \1, including colons. (What Emacs actually did is way > more complicated than that, but that was the idea.)
Ah, OK -- I should have realized that would be the case (rather than just doing simple splitting at colons). > Of course this loses if the :[0-9]: pattern happens to match > elsewhere in the error message, but in reality ... (and what > emacs 22 does is something different again, as I understand it). OK, I guess I ought to take some time to test Emacs (and Vim and some other apps that have built-in support for parsing GNU-style error messages) and see what they actually do if I feed them a URI for the source-file-name part). And/or look at the code to see what regexp or other mechanism they use to parse the error messages. > I'll forward your message to rms and go from there. Thanks -- I appreciate it --Mike -- Michael(tm) Smith http://people.w3.org/mike/ http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
