Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg I think the attached should be safe now and will commit it
Georg unless somebody finds other problems.
Seems fine to me.
JMarc
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> I think the attached should be safe now and will commit it
Georg> unless somebody finds other problems.
Seems fine to me.
JMarc
Am Dienstag, 14. September 2004 11:22 schrieb Jean-Marc Lasgouttes:
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg Any sort of files can be inserted with the include inset (at
Georg least if you use the verbatim mode). So it is possible best to
Georg deactivate the load button if the
Am Dienstag, 14. September 2004 11:22 schrieb Jean-Marc Lasgouttes:
> > "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
>
> Georg> Any sort of files can be inserted with the include inset (at
> Georg> least if you use the verbatim mode). So it is possible best to
> Georg> deactivate the
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg Loading an included file results in an error message if it is
Georg not a lyx file. This can be fixed easily, see attached. There
Georg is still an error message if no editor for the file format is
Georg known, but the user can fix that by
Am Dienstag, 14. September 2004 09:39 schrieb Jean-Marc Lasgouttes:
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg Loading an included file results in an error message if it is
Georg not a lyx file. This can be fixed easily, see attached. There
Georg is still an error message if no
Georg == Georg Baum [EMAIL PROTECTED] writes:
What kind of files do you plan to insert this way? Is that meant
for .tex or .txt files? I do not think these ones are well suited
for getExtFromContents.
Georg Any sort of files can be inserted with the include inset (at
Georg least if you use
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Loading an included file results in an error message if it is
Georg> not a lyx file. This can be fixed easily, see attached. There
Georg> is still an error message if no editor for the file format is
Georg> known, but the user can fix
Am Dienstag, 14. September 2004 09:39 schrieb Jean-Marc Lasgouttes:
> > "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
>
> Georg> Loading an included file results in an error message if it is
> Georg> not a lyx file. This can be fixed easily, see attached. There
> Georg> is still an error
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
>> What kind of files do you plan to insert this way? Is that meant
>> for .tex or .txt files? I do not think these ones are well suited
>> for getExtFromContents.
Georg> Any sort of files can be inserted with the include inset (at
Georg>
On Sat, 16 Sep 2000, Dekel Tsur wrote:
On Fri, Sep 15, 2000 at 07:32:28PM +0300, Marko Vendelin wrote:
The following patch adds support for regexp search in FormCitation (Gnome
frontend).
Why not filter the entries in the citation list (i.e. show only the ones
containing the
On Sat, 16 Sep 2000, Dekel Tsur wrote:
> On Fri, Sep 15, 2000 at 07:32:28PM +0300, Marko Vendelin wrote:
> >
> > The following patch adds support for regexp search in FormCitation (Gnome
> > frontend).
>
> Why not filter the entries in the citation list (i.e. show only the ones
> containing
On Fri, Sep 15, 2000 at 07:32:28PM +0300, Marko Vendelin wrote:
The following patch adds support for regexp search in FormCitation (Gnome
frontend).
Why not filter the entries in the citation list (i.e. show only the ones
containing the regexp) instead of search?
On Fri, Sep 15, 2000 at 07:32:28PM +0300, Marko Vendelin wrote:
>
> The following patch adds support for regexp search in FormCitation (Gnome
> frontend).
Why not filter the entries in the citation list (i.e. show only the ones
containing the regexp) instead of search?
Marko Vendelin [EMAIL PROTECTED] writes:
| On 15 Sep 2000, Lars Gullik Bjønnes wrote:
|
| | Any good library (C/C++) which is able to check whether a string matches
| | given regexp. Return value TRUE/FALSE/invalid regexp is expected :)
|
| We already have that included under src/support
On 15 Sep 2000, Lars Gullik Bjønnes wrote:
One not however: do not use defines, ever!
#define CONF_COLUMN "column"
should be
static string const CONF_COLUMN("column");
I will submit a patch with all these defines removed. But can you tell me
why should we avoid the defines (I
Marko Vendelin [EMAIL PROTECTED] writes:
| On 15 Sep 2000, Lars Gullik Bjønnes wrote:
|
| One not however: do not use defines, ever!
|
| #define CONF_COLUMN "column"
|
| should be
|
| static string const CONF_COLUMN("column");
|
| I will submit a patch with all these defines
Marko Vendelin <[EMAIL PROTECTED]> writes:
| On 15 Sep 2000, Lars Gullik Bjønnes wrote:
|
| > | Any good library (C/C++) which is able to check whether a string matches
| > | given regexp. Return value TRUE/FALSE/invalid regexp is expected :)
| >
| > We already have that included under
On 15 Sep 2000, Lars Gullik Bjønnes wrote:
> One not however: do not use defines, ever!
>
> #define CONF_COLUMN "column"
>
> should be
>
> static string const CONF_COLUMN("column");
I will submit a patch with all these defines removed. But can you tell me
why should we avoid the
Marko Vendelin <[EMAIL PROTECTED]> writes:
| On 15 Sep 2000, Lars Gullik Bjønnes wrote:
|
| > One not however: do not use defines, ever!
| >
| > #define CONF_COLUMN "column"
| >
| > should be
| >
| > static string const CONF_COLUMN("column");
|
| I will submit a patch with all these
20 matches
Mail list logo
