On Fri, 2024-08-16 at 10:10 +0100, José Matos wrote:
> Question:
> Does anyone have a reason to keep the current two stages process?
The new code becomes simply:
def crop_files(pnmcrop, basename):
for file in glob.glob(f"{basename}*.ppm"):
tmp = tempfile.TemporaryFile()
conv_c
On Fri, 2024-08-16 at 10:10 +0100, José Matos wrote:
> Hi,
> my main focus now is to try to clean the python scripts that we
> use.
One question that I noticed while searching for this.
Is it possible now to use preview when using minted?
minted requires to invoke LaTeX with the -shell-escape
Hi,
my main focus now is to try to clean the python scripts that we use.
Musing:
I need to look immediately into the preview stuff since I found that in
python 3.13 the pipe module is gone (it is a small wrap around
os.popen).
The only place where we use it to call consecutively pnmcrop with
op
Jean-Pierre Chrétien wrote:
> PS I noticed that the same phrase "Replace word with current choice" is in
> the tooltips for "Find next", "Replace" and "Replace all". This is the
> correct phrase only for the second one.
this is now fixed. pavel
Stephan Witt a écrit :
Am 08.04.2011 um 09:38 schrieb Jean-Pierre Chrétien:
Abdelrazak Younes a écrit :
On 04/03/2011 08:38 PM, Jean-Pierre Chrétien wrote:
Hello,
Using the spellchecker window, I get this quite often when I hit 'Ignore all':
We reached the end of the document, would you li
Am 08.04.2011 um 09:38 schrieb Jean-Pierre Chrétien:
> Abdelrazak Younes a écrit :
>> On 04/03/2011 08:38 PM, Jean-Pierre Chrétien wrote:
>>> Hello,
>>>
>>> Using the spellchecker window, I get this quite often when I hit 'Ignore
>>> all':
>>>
>>>
>>> We reached the end of the document, would
Abdelrazak Younes a écrit :
On 04/03/2011 08:38 PM, Jean-Pierre Chrétien wrote:
Hello,
Using the spellchecker window, I get this quite often when I hit
'Ignore all':
We reached the end of the document, would you like to continue from
the beginning?
If I say yes, it restars at the beginn
Am 04.04.2011 um 13:02 schrieb Stephan Witt:
> Am 04.04.2011 um 11:39 schrieb Abdelrazak Younes:
>
>> On 04/03/2011 08:38 PM, Jean-Pierre Chrétien wrote:
>>> Hello,
>>>
>>> Using the spellchecker window, I get this quite often when I hit 'Ignore
>>> all':
>>>
>>>
>>> We reached the end of the
Am 04.04.2011 um 11:39 schrieb Abdelrazak Younes:
> On 04/03/2011 08:38 PM, Jean-Pierre Chrétien wrote:
>> Hello,
>>
>> Using the spellchecker window, I get this quite often when I hit 'Ignore
>> all':
>>
>>
>> We reached the end of the document, would you like to continue from the
>> beginni
On 04/03/2011 08:38 PM, Jean-Pierre Chrétien wrote:
Hello,
Using the spellchecker window, I get this quite often when I hit
'Ignore all':
We reached the end of the document, would you like to continue from
the beginning?
If I say yes, it restars at the beginning, which is not what I want
Hello,
Using the spellchecker window, I get this quite often when I hit 'Ignore all':
We reached the end of the document, would you like to continue from the
beginning?
If I say yes, it restars at the beginning, which is not what I want.
If I say no, it goes on where I was, which is I want,
Il 15/07/2010 05:07, Richard Heck ha scritto:
On 07/14/2010 10:49 PM, Jacob Barandes wrote:
Now two feature questions about 2.0. Is there any possibility that
the advanced search might support wildcards? That way if a user needs
to change, say, x^{} to x_{} for various possible
choices of , th
On 07/14/2010 10:49 PM, Jacob Barandes wrote:
Hi,
LyX is working great, and alpha4 is looking excellent.
First, a question. I can build 2.0-alpha4, and its additional features
(like the advanced search) nicely augment my install of 1.6 when I
need ot use them, but I'd like it to
Hi,
LyX is working great, and alpha4 is looking excellent.
First, a question. I can build 2.0-alpha4, and its additional features (like
the advanced search) nicely augment my install of 1.6 when I need ot use
them, but I'd like it to use a different local user config directory (i.e.,
not ~
Mikhail Petrov wrote:
> Probably, it would be a good improvement of further LyX versions if it
> allow one to set TeX encodings for each document like it is realized for
> input encoding of the source.
LyX 2.0 will have this.
Jürgen
Dear developers,
Recently, I installed latest version of LyX and found an unreasonable property
of the application. Namely, there is impossible to select different TeX font
encodings for different documents because the selecting of the variable
\font_encoding is only available in global prefere
Philippe Charpentier wrote:
I just test rev. 27282:
- for the question of excluding modules, it works now if the class
contain the tag ExcludesModule, that is:
if I create a new document with the class "article (AMS)" then the
module "theorems-ams" is loaded; if
I change to the class "article (A
Richard Heck a écrit :
> rgheck wrote:
>> Charpentier Philippe wrote:
>>> For the first question:
>>> if I put
>>> ExcludesModule theorems-ams
>>> in my class then changing from "article (AMS)" to "article (AMS)
>>> Francais"
>>> has the consequence that no module is loaded which is not very nice
>
rgheck wrote:
Charpentier Philippe wrote:
For the first question:
if I put
ExcludesModule theorems-ams
in my class then changing from "article (AMS)" to "article (AMS)
Francais"
has the consequence that no module is loaded which is not very nice I
think...
OK. I'll look at this. The algorith
Charpentier Philippe wrote:
rgheck a écrit :
rgheck wrote:
Charpentier Philippe wrote:
Similarly, if I create a document in the class "article (AMS) en
Français"
the module "theorems-ams-fr" is automatically loaded but the
modules "theorems-ams", "theorems-starred" and "theorems-std"
can stil
rgheck a écrit :
rgheck wrote:
Charpentier Philippe wrote:
Similarly, if I create a document in the class "article (AMS) en
Français"
the module "theorems-ams-fr" is automatically loaded but the
modules "theorems-ams", "theorems-starred" and "theorems-std"
can still be loaded (although they ar
Jürgen Spitzmüller wrote:
> > Jurgen will know what to do, I hope: The change is needed in
> > GuiDocument::loadModuleInfo().
>
> Yes, I have a fix in the pipe.
Should be fixed now (rev. 27248).
Jürgen
rgheck wrote:
> Jurgen will know what to do, I hope: The change is needed in
> GuiDocument::loadModuleInfo().
Yes, I have a fix in the pipe.
Jürgen
rgheck wrote:
Charpentier Philippe wrote:
Similarly, if I create a document in the class "article (AMS) en
Français"
the module "theorems-ams-fr" is automatically loaded but the
modules "theorems-ams", "theorems-starred" and "theorems-std"
can still be loaded (although they are excluded in "the
Charpentier Philippe wrote:
Hi,
if you define a new module whose name contains non ASCII
characters, like
#\DeclareLyXModule{Théoremes (AMS) Francais}
then lyx-1.6 crashes with the following output:
lassert.cpp(21): ASSERTION static_cast(ascii[i]) < 0x80
VIOLATED IN docstring.cpp:50
Assertion
Hi,
if you define a new module whose name contains non ASCII
characters, like
#\DeclareLyXModule{Théoremes (AMS) Francais}
then lyx-1.6 crashes with the following output:
lassert.cpp(21): ASSERTION static_cast(ascii[i]) < 0x80
VIOLATED IN docstring.cpp:50
Assertion triggered in void lyx::doAss
Michal Skrzypek wrote:
> I wanted to report something relatively harmless, but strange. I am
> currently using LyX 1.5.2 (XP SP2, Polish version). I apologize that I
> cannot check this with the current version, but for now I cannot
> upgrade/test it due to time constraints, as I am nearing the com
Those few files regarding building of lyx, have some vague warnings
about using system boost instead of included one. What is the real
current situation in this matter - Lyx version 1.5.3, Boost version
1.34.1.
Martin Vermeer wrote:
On Thu, 04 Oct 2007 22:10:25 +0200
Helge Hafting <[EMAIL PROTECTED]> wrote:
I tried making a custom inset, and found that
if I don't specify "Font . . . EndFont", then LyX crashes
as soon as I try "Insert->Custom Insets->my inset"
I didn't want to specify a font, I tho
On Thu, 04 Oct 2007 22:10:25 +0200
Helge Hafting <[EMAIL PROTECTED]> wrote:
> I tried making a custom inset, and found that
> if I don't specify "Font . . . EndFont", then LyX crashes
> as soon as I try "Insert->Custom Insets->my inset"
>
> I didn't want to specify a font, I though LyX could use
On Thu, Oct 04, 2007 at 10:10:25PM +0200, Helge Hafting wrote:
> I tried making a custom inset, and found that
> if I don't specify "Font . . . EndFont", then LyX crashes
> as soon as I try "Insert->Custom Insets->my inset"
>
> I didn't want to specify a font, I though LyX could use whatever f
Helge Hafting wrote:
Second bug:
I had this:
#\DeclareLyXModule[multicol.sty]{Adds support for text in multiple
columns}{Multicol}
So I expected multicol.sty to load automatically, but no. I had to add
that to "Preamble...EndPreamble" as well. What is the purpose
of having [multicol.sty] in de
I tried making a custom inset, and found that
if I don't specify "Font . . . EndFont", then LyX crashes
as soon as I try "Insert->Custom Insets->my inset"
I didn't want to specify a font, I though LyX could use whatever font
that was in effect at the moment. Some cases don't need to
set a font, t
Hi,
I notice the following small bug in amsart-plain.layout:
Input amsart.layout -> Input amsdef.inc -> Input ammsmath.inc
Input amsmaths-plain.inc
Thus both Theorem and Theorem* appear in the layout combobox, which is not
useful, and if you choose both you get a LaTeX error as they define the
Bo> I am adding this to the trunk, and I will have to ask JMarc for
Bo> putting this to 1.4.x (after he gets back from vacation).
Please apply it (or do you want me to do it?)
Done.
Bo
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
>> Many thanks, it works perfectly. If possible please add this to the
>> 1.4.x tree and to trunk.
Bo> I am adding this to the trunk, and I will have to ask JMarc for
Bo> putting this to 1.4.x (after he gets back from vacation).
Please apply it (
Many thanks, it works perfectly. If possible please add this to the
1.4.x tree and to trunk.
I am adding this to the trunk, and I will have to ask JMarc for
putting this to 1.4.x (after he gets back from vacation).
Cheers,
Bo
Bo Peng wrote:
Please test the attached patch, which reads output from latex
immediately after they are available.
Many thanks, it works perfectly. If possible please add this to the
1.4.x tree and to trunk.
thanks and regards
Uwe
I will see what I can do.
Please test the attached patch, which reads output from latex
immediately after they are available.
Cheers,
Bo
Index: lib/configure.py
===
--- lib/configure.py (revision 14498)
+++ lib/configure.py (workin
The old configure script (for the sh-shell) printed out which
LaTeX-package is currently cecked for so that the user got a feedback.
configure.py only prints "+checking list of textclasses... " but not the
name of the currently checked package.
Why was this feature not implemented in configure.p
Hi Bo,
When I install LyX on a fresh LaTeX (in my case MiKTeX) system,
configure.py checks for LaTeX-packages. This check invokes MiKTeX to
automatically install missing packages - a nice feature that could cost
some time when you only have a slow internet conection.
The problem is that the us
Helge Hafting <[EMAIL PROTECTED]> writes:
| Georg Baum wrote:
>
>>Helge Hafting wrote:
>>
>>
>>>1. Translations that doesn't work:
>>>The menu items "Tools" and "New from template",
>>>and quite a few other strings are untranslateable.
>>>Some of these actually have a translation in the existing f
Helge Hafting wrote:
> Georg Baum wrote:
>
>>Helge Hafting wrote:
>>
>>Find out why it does not work?
>>
>>
> Which is why I asked the question.
> I have no idea what failure modes a "po" file can have.
Me neither. Therefore I asked that stupid question :-)
> Should I fix the line numbers in
> "Helge" == Helge Hafting <[EMAIL PROTECTED]> writes:
Helge> Which is why I asked the question. I have no idea what failure
Helge> modes a "po" file can have. I edit the strings, and sometimes
Helge> the translated text isn't used by lyx. I don't know why.
If a translation is marked
#, fuzzy
Georg Baum wrote:
Helge Hafting wrote:
1. Translations that doesn't work:
The menu items "Tools" and "New from template",
and quite a few other strings are untranslateable.
Some of these actually have a translation in the existing file,
but it doesn't take. The english text remains while a
Helge Hafting wrote:
> 1. Translations that doesn't work:
> The menu items "Tools" and "New from template",
> and quite a few other strings are untranslateable.
> Some of these actually have a translation in the existing file,
> but it doesn't take. The english text remains while all my other
> c
Helge Hafting <[EMAIL PROTECTED]> writes:
| 2. Obviously wrong translations:
| Not bad work by the previous translator,
:-)
| but stuff that can't be right
| because the translated string have nothing at all to do with the message.
| It may even be another unrelated _english_ string where
| the
Attached: Lots of strings translated into Norwegian.
During translation, I have found some problem with the no.po file:
1. Translations that doesn't work:
The menu items "Tools" and "New from template",
and quite a few other strings are untranslateable.
Some of these actually have a translation
Lars Gullik Bjønnes wrote:
> use "grep -i" please.
;-) I see light!
--
Angus
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Thanks Lars. I note however that none of the supported layouts
Angus> appear to use this mechanism at all...
Angus> Why not?
Angus> $ grep provides lib/layouts/*
hat about
fantomas[ssh]: cd lib/layouts/
fantomas[ssh]: grep -i p
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> Yes.
>>
>> It the provide support in .layout files. We do not have generic
>> support for this, but have
>>
>> providesamsmath
>> providesmakeidx
>> providesnatbib
>> providesurl
>>
>> So the natbib you need is already th
On Wed, Oct 22, 2003 at 05:22:12PM +0200, Lars Gullik Bjønnes spake thusly:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | That reminds me...
> >
> | I have had some correspondence recently with a user of the AGU latex
> | classes. Apparently they add the equivalent of '\usepackage[AGU's set
Lars Gullik Bjønnes wrote:
> Yes.
>
> It the provide support in .layout files. We do not have generic
> support for this, but have
>
> providesamsmath
> providesmakeidx
> providesnatbib
> providesurl
>
> So the natbib you need is already there, you just have to set it in
> the .layout file.
Tha
Angus Leeming <[EMAIL PROTECTED]> writes:
>> Hmmm, writing support for AGU's new DTD using Docbook as a starting
>> point. I have obtained a description + test documents and it looks
>> very much like a feasible job.
>>
>> This would have two-fold usefulness: (1) it makes LyX (more) useful
>> for
> Hmmm, writing support for AGU's new DTD using Docbook as a starting
> point. I have obtained a description + test documents and it looks
> very much like a feasible job.
>
> This would have two-fold usefulness: (1) it makes LyX (more) useful
> for the community of AGU journal contributors, and (
On Wed, Feb 12, 2003 at 11:02:52AM +, Angus Leeming wrote:
> Thank you. All is clearer now. Would verbatimItem return '4.5 \columnwidth'
> too?
Yes. It looks for something within balanced braces. Not entirely correct,
but not too far off.
> One more thing: LyX can read all of minipage's opti
On Wednesday 12 February 2003 10:55 am, Andre Poenitz wrote:
> On Wed, Feb 12, 2003 at 10:50:30AM +, Angus Leeming wrote:
> > >> Sure. One question. Would ' - 4,5 cM ' count as one token or two?
> > >
> > > Six. - 4 5 , c M.
> > >
> > > The conversion has to be done on output.
> >
> > ??? Ok.
On Wed, Feb 12, 2003 at 10:50:30AM +, Angus Leeming wrote:
> >> Sure. One question. Would ' - 4,5 cM ' count as one token or two?
> >
> > Six. - 4 5 , c M.
> >
> > The conversion has to be done on output.
>
> ??? Ok. You tokenise and then parse. Fair enough.
But wrong. Tokenization should
Andre Poenitz wrote:
> On Wed, Feb 12, 2003 at 10:06:56AM +, Angus Leeming wrote:
>> > Currently I like the idea of tex2lyx being small and independent very
>> > much.
>>
>> Sure. One question. Would ' - 4,5 cM ' count as one token or two?
>
> Six. - 4 5 , c M.
>
> The conversion has to be
On Wed, Feb 12, 2003 at 10:06:56AM +, Angus Leeming wrote:
> > Currently I like the idea of tex2lyx being small and independent very much.
>
> Sure. One question. Would ' - 4,5 cM ' count as one token or two?
Six. - 4 5 , c M.
The conversion has to be done on output.
Andre'
--
Those who
-BEGIN PGP SIGNED MESSAGE-
On Mittwoch, 12. Februar 2003 10:21, Angus Leeming wrote:
...
>
> $ ./trial ' - 3.5 cM' ' + 4,5 Cm ' ' + 4.5 \columnWidth '
> ' - 3.5 cM' becomes '-3.5cm'
> ' + 4,5 Cm ' becomes '+4.5cm'
> ' + 4.5 \columnWidth ' becomes '+4.5\columnWidth'
You may miss '.3 cm'
>
On Wednesday 12 February 2003 9:40 am, Andre Poenitz wrote:
> On Wed, Feb 12, 2003 at 09:38:06AM +, Angus Leeming wrote:
> > Should I write the equivalent of this as a function for tex2lyx using the
> > boost regex library?
>
> Overkill.
>
> Better use a simple loop over the string than adding
On Wed, Feb 12, 2003 at 11:00:33AM +0100, Jean-Marc Lasgouttes wrote:
> While I agree about being independent from boost, you will have to
> have some dependency on the lyx sources: the parsing of things like
> \section depends on the .layout files, and I do not think it would be
> wise to do a re-
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> Currently I like the idea of tex2lyx being small and
Andre> independent very much.
While I agree about being independent from boost, you will have to
have some dependency on the lyx sources: the parsing of things like
\section dep
On Wed, Feb 12, 2003 at 09:38:06AM +, Angus Leeming wrote:
> Should I write the equivalent of this as a function for tex2lyx using the
> boost regex library?
Overkill.
Better use a simple loop over the string than adding a dependance on boost
stuff.
Currently I like the idea of tex2lyx bein
On Wednesday 12 February 2003 9:31 am, Andre Poenitz wrote:
> On Wed, Feb 12, 2003 at 09:21:12AM +, Angus Leeming wrote:
> > > And I believe '4.5 Cm' and '4.5 cM' are valid as well...
> >
> > Geeez.
>
> Someone should check it first
That's why I gave you a little program to run, you noodle
On Wed, Feb 12, 2003 at 09:21:12AM +, Angus Leeming wrote:
> > And I believe '4.5 Cm' and '4.5 cM' are valid as well...
>
> Geeez.
Someone should check it first
> Would this suffice do you think?
> $LatexLength =~ s/^\s*([+-]?)\s*(\d+)[.,]?(\d*)\s*/$1$2.$3/;
> # Now ensu
Andre Poenitz wrote:
> On Tue, Feb 11, 2003 at 09:47:13PM +0100, Georg Baum wrote:
>> Am Dienstag, 11. Februar 2003 12:00 schrieb Angus Leeming:
>> > I have a trivial patch to the reLyX minibuffer output:
>> >
>> > * reLyX/BasicLyX.pm: Wrap minipage width and height output in
>> >
On Tue, Feb 11, 2003 at 09:47:13PM +0100, Georg Baum wrote:
> Am Dienstag, 11. Februar 2003 12:00 schrieb Angus Leeming:
> > I have a trivial patch to the reLyX minibuffer output:
> >
> > * reLyX/BasicLyX.pm: Wrap minipage width and height output in
> > inverted commas to keep the L
Am Dienstag, 11. Februar 2003 12:00 schrieb Angus Leeming:
> I have a trivial patch to the reLyX minibuffer output:
>
> * reLyX/BasicLyX.pm: Wrap minipage width and height output in
> inverted commas to keep the LyX parser happy with "4.5 cm".
> (Note the space.)
While you
On Tue, Feb 11, 2003 at 03:02:52PM +0100, Jean-Marc Lasgouttes wrote:
> Andre> Of course, if at one point of time the format has evolved too
> Andre> far, tex2lyx might get an update.
>
> Like reLyX that produces a strange file format with a mix of old
> constructs and new ones...
Not necessarily
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> But it has certain benefits:
Andre> - No dependence on LyX proper. - Small. - No need to access
Andre> fragile LyX internals.
Indeed. But at least, when the internals change, you know about it
because it does not compile anymore
On Tue, Feb 11, 2003 at 02:46:48PM +0100, Jean-Marc Lasgouttes wrote:
> Andre> The tokenizer should be ok unless someone starts changing
> Andre> catcodes ore redefines macros. The "backend" (i.e. writing the
> Andre> proper .lyx constructs) is far from working, let alone
> Andre> complete...
>
>
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> The tokenizer should be ok unless someone starts changing
Andre> catcodes ore redefines macros. The "backend" (i.e. writing the
Andre> proper .lyx constructs) is far from working, let alone
Andre> complete...
Are you sure that prod
On Tuesday 11 February 2003 1:21 pm, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
> | > $ mkdir src/tex2lyx/.deps
> | > $ touch src/tex2lyx/.deps/tex2lyx.Po
> | >
> | > solves the problem. Should it be generated automatically or cvs added?
>
> No!
>
> That was something wr
Andre Poenitz <[EMAIL PROTECTED]> writes:
| > $ mkdir src/tex2lyx/.deps
| > $ touch src/tex2lyx/.deps/tex2lyx.Po
| >
| > solves the problem. Should it be generated automatically or cvs added?
No!
That was something wrong on your end.
a autogen, re-configure, make distclean etc would have fixed
On Tue, Feb 11, 2003 at 01:12:33PM +, Angus Leeming wrote:
> As JMarc noted yesterday, this approach:
> else if (t.cs() == "usepackage") {
> string const options = getArg('[', ']');
> string const name = getArg('{', '}');
>
On Tue, Feb 11, 2003 at 12:51:24PM +, Angus Leeming wrote:
> I wonder too. However, my motivation has been:
> 1. learn enough perl to feel comfortable when confronted with it.
> 2. LyX 1.3 will be around for at least 6 months.
Currently there is no dependency on LyX in tex2lyx (quite contrary
Andre Poenitz wrote:
> On Tue, Feb 11, 2003 at 11:00:37AM +, Angus Leeming wrote:
>> I have a trivial patch to the reLyX minibuffer output:
>>
>> * reLyX/BasicLyX.pm: Wrap minipage width and height output in
>> inverted commas to keep the LyX parser happy with "4.5 cm".
>>
On Tuesday 11 February 2003 12:39 pm, Andre Poenitz wrote:
> On Tue, Feb 11, 2003 at 11:00:37AM +, Angus Leeming wrote:
> > I have a trivial patch to the reLyX minibuffer output:
> >
> > * reLyX/BasicLyX.pm: Wrap minipage width and height output in
> > inverted commas to keep th
On Tue, Feb 11, 2003 at 11:00:37AM +, Angus Leeming wrote:
> I have a trivial patch to the reLyX minibuffer output:
>
> * reLyX/BasicLyX.pm: Wrap minipage width and height output in
> inverted commas to keep the LyX parser happy with "4.5 cm".
> (Note the space.)
>
> H
I have a trivial patch to the reLyX minibuffer output:
* reLyX/BasicLyX.pm: Wrap minipage width and height output in
inverted commas to keep the LyX parser happy with "4.5 cm".
(Note the space.)
However, I wonder whether I should do this or whether I should strip out the
On Tue, Dec 10, 2002 at 08:12:16PM +0100, Lina Yordanova wrote:
> Haloo,
> I would like to insert and process text in bulgarian language in lyx. I used
> to have phonetic bulgarian keyboard in other applications but in lyx I
> suspect it is impossible.
> 1. Only bg-bds-cp1251.kmap is availabl
Haloo,
I would like to insert and process text in bulgarian language in lyx. I used
to have phonetic bulgarian keyboard in other applications but in lyx I
suspect it is impossible.
1. Only bg-bds-cp1251.kmap is available in /usr/share/lyx/kbd.
2. When I tried a kmap file form another package f
On Friday 06 December 2002 5:28 pm, Angus Leeming wrote:
> > gives "Unknown function"
>
> U. It looks like all the interesting ones are missed. I'll dig into
> xforms.
The phrase "wilfully perverse" springs to mind...
Does anyone have any idea why they attempt this weirdness and not pass the
On Friday 06 December 2002 3:56 pm, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | On Friday 06 December 2002 12:23 pm, Lars Gullik Bjønnes wrote:
> >> mmm... we had a huge party at work yesterday... 13 hour party...
> |
> | Well here's some nice news for a sore head. I
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Friday 06 December 2002 12:23 pm, Lars Gullik Bjønnes wrote:
>> mmm... we had a huge party at work yesterday... 13 hour party...
>
| Well here's some nice news for a sore head. I finally got it into my head
| that all that KEYPRESS rubbish in XWorkAr
On Friday 06 December 2002 12:23 pm, Lars Gullik Bjønnes wrote:
> mmm... we had a huge party at work yesterday... 13 hour party...
Well here's some nice news for a sore head. I finally got it into my head
that all that KEYPRESS rubbish in XWorkArea was to work-around xforms
limitations/bugs.
S
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Friday 06 December 2002 11:47 am, Lars Gullik Bjønnes wrote:
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>> | Lars, could you give me a brief précis of what you're talking about here
>> | and what the xforms bug is/was. Does it still exist with xform
On Friday 06 December 2002 11:47 am, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | Lars, could you give me a brief précis of what you're talking about here
> | and what the xforms bug is/was. Does it still exist with xforms 1.0?
>
> Sometimes xforms just return key=0 ev
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars, could you give me a brief précis of what you're talking about here and
| what the xforms bug is/was. Does it still exist with xforms 1.0?
Sometimes xforms just return key=0 even if a key is pressed... or
something. Or perhaps it is that keysum is
Lars, could you give me a brief précis of what you're talking about here and
what the xforms bug is/was. Does it still exist with xforms 1.0?
Do we ever get to that
} else
break;
point?
Angus
// Note that we need this handling because of a bug
// in XFor
On Friday 02 August 2002 2:42 pm, Dekel Tsur wrote:
> On Fri, Aug 02, 2002 at 12:37:11PM +0100, Angus Leeming wrote:
> > However...
> >
> > I think I've come to the opposite conclusion. If we overload addPreview
> > then things like tables could generate a preview of the entire table if
> > they s
On Fri, Aug 02, 2002 at 12:37:11PM +0100, Angus Leeming wrote:
> However...
>
> I think I've come to the opposite conclusion. If we overload addPreview then
> things like tables could generate a preview of the entire table if they so
> desired.
If you want to preview a table, you can always ov
On Friday 02 August 2002 12:50 pm, Dekel Tsur wrote:
> On Thu, Aug 01, 2002 at 02:13:50PM +0100, Angus Leeming wrote:
> > How should I loop over all insets? Do I:
> >
> > 1. Loop from outside
> > for (; it != end; ++it) {
> > (*it)->addPreview(ploader);
> > // add some
On Thu, Aug 01, 2002 at 02:13:50PM +0100, Angus Leeming wrote:
> How should I loop over all insets? Do I:
>
> 1. Loop from outside
> for (; it != end; ++it) {
> (*it)->addPreview(ploader);
> // add some sub-loop
> }
>
> 2. Overload addPreview in container
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Thursday 01 August 2002 2:58 pm, Lars Gullik Bjønnes wrote:
>> | Incidentally, what's the preferred STL algorithm for
>> |for (; it != end; ++it) {
>> |(*it)->addPreview(ploader);
>> |}
>>
>> some variant of
>>
>> for_each(be
On Thursday 01 August 2002 2:58 pm, Lars Gullik Bjønnes wrote:
> | Incidentally, what's the preferred STL algorithm for
> | for (; it != end; ++it) {
> | (*it)->addPreview(ploader);
> | }
>
> some variant of
>
> for_each(begin, end, bind(&Type::addPreview, ref(ploader)));
Angus Leeming <[EMAIL PROTECTED]> writes:
| Before I dive into this caching stuff I'd like to finish the preview clean-up
| that started it off.
>
| The code below iterates over only "top level" insets that are owned directly
| by the Buffer.
>
| void Previews::generateBufferPreviews(Buffer con
Before I dive into this caching stuff I'd like to finish the preview clean-up
that started it off.
The code below iterates over only "top level" insets that are owned directly
by the Buffer.
void Previews::generateBufferPreviews(Buffer const & buffer) const
{
PreviewLoader & ploader =
1 - 100 of 110 matches
Mail list logo