On 23/02/2009, at 7:15 AM, DaveS wrote:
>
Obviously the number one priority is ensuring that parsing works
correctly
on all platforms. Could we do a bit of inspection and do a best
choice
based on the user's platform. Barring that, how about exposing this
so a
knowledgeable user can specify a value if they choose.
Another idea occurred to me. The mode of the new file is almost
certainly going to match that of the parsed parent file. In other
words, if we are parsing a c++ file, then all of the #included files
can be parsed as c++ as well. Hence as a fallback, if after loading
the file with find-file-noselect we find that there is no mode set, we
can attempt to parse it using whatever the parent (not sure if that's
the right terminology here) file's mode is.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta