Il 06/06/2011 10:09, Andrew Parsloe ha scritto:
3. The backslash and Latex completion hints
As soon as I enter a backslash in a regexp inset, it generates a Latex
completion hint. The backslash alone has \! suggested; \a produces
\alpha as a hint, and so on. I think these hints should be turned off
for the regexp inset since the stuff being entered in the inset is not
Latex code. For instance if you follow the suggestion and enter
\alpha, the resulting regexp will not find alpha in a maths inset.
so, in the upcoming 2.0.1, latex completion hints and entering of macros
have been disabled in regexp insets. Now, when typing a '\', just
inserts a '\' character in the regular expression (normally useful for
escape sequences and for matching special chars such as '\' itself or
parentheses). Also, the '^' and '_' characters now are just entered
normally without the need for backslash-ing them. Note that '^' has a
special meaning in regular expressions, so if you want to match a '^'
character you need to enter '\^'.
I know little about regexps so I was trying to duplicate in LyX what
is described in the documentation that comes with TeXworks (that comes
with MikTeX). It says "As TEXworks is built on Qt4, the available
regular expressions ... are a subset of those found in Qt4." I thought
the same might be true of LyX.
the allowed regular expressions are in principle those ones found in the
boost/regex library, which should be compatible with Perl ones to a
large extent. This needs surely to be clarified in the documentation,
however for now the regular expressions feature is in a
prototype/evolving state (as you correctly pointed out), so we'll
certainly update the docs once the feature is a little bit more stable.
5. Where is the cursor after an unsuccessful search?
If a search is unsuccessful, the cursor seems to disappear from the
main window. My expectation is that for a failed search it should be
located at exactly the place it was before executing the search.
On Linux I can't see this problem (on a failed search the cursor is
exactly where it was on the main document before the search started).
Probably it's related to the Qt version. However, we have in other
scenarios a similar issue of the focus being where it should not be
(apparently it being "nowhere"), e.g., see #7561 for one of these
focusing issues. Perhaps addressing them will solve also your particular
case, but I'm not sure.
Bye,
T.
