[EMAIL PROTECTED] writes:
| Author: rgheck
| Date: Thu May 24 19:17:04 2007
| New Revision: 18494
|
| URL: http://www.lyx.org/trac/changeset/18494
| Log:
| Fix for bugs 2199 and 3667. Most of the changes were to the logic. Buffers
| that were opened for possible included LyX files need to be closed if those
| files cannot be loaded, for example. A bit more work was needed to allow a
| LyX file to include itself as a verbatim or listings without trying to load
| itself and without relying upon loadIfNeeded() to report the problem.
|
| Modified:
| lyx-devel/trunk/src/LyXFunc.cpp
| lyx-devel/trunk/src/insets/InsetInclude.cpp
|
| Modified: lyx-devel/trunk/src/insets/InsetInclude.cpp
| URL:
http://www.lyx.org/trac/file/lyx-devel/trunk/src/insets/InsetInclude.cpp?rev=18494
| ==============================================================================
| --- lyx-devel/trunk/src/insets/InsetInclude.cpp (original)
| +++ lyx-devel/trunk/src/insets/InsetInclude.cpp Thu May 24 19:17:04 2007
| @@ -230,6 +230,13 @@
| }
|
|
| +bool isInputOrInclude(InsetCommandParams const & params)
| +{
| + Types const t = type(params);
| + return (t == INPUT) or (t == INCLUDE);
| +}
We have not used 'or', 'and' until now, and I see no or little reason
to begin using them. Apart from making the code in-consistent that is.
Please change :-)
--
Lgb
