On Fri, Jan 21, 2005 at 09:57:48PM +, Angus Leeming wrote:
> Cygwin's POSIX emulation layer avoids
> the need for the various workarounds required when using other
> compilers under MS-Windows.
See! See! I *am* speaking from real experience! I'm not just some
idiot talking out his ass like
On Thu, Jan 20, 2005 at 01:09:21AM +0100, Uwe Stöhr wrote:
> Hello LyXers,
>
> since LyX 1.2.x a figure is by default inserted into a float as a
> justified paragraph instead of a centered one. This behaviour is very
> annoying for many users (me too) because one have to use the menu Layout
> -
On Sat, Jan 22, 2005 at 09:50:51AM +0100, Andre Poenitz wrote:
> On Tue, Jan 18, 2005 at 07:36:36AM -0500, John Weiss wrote:
> > On Mon, Jan 17, 2005 at 02:09:33PM +0100, Lars Gullik Bjønnes wrote:
> > >
> > > I feel we are beginning on a slippery slope now... ok to support
> > > windows if only m
On Thu, Jan 20, 2005 at 01:44:58PM +0100, Asger Ottar Alstrup wrote:
> Hi,
>
> The result of today's work is this: Everything compiles with the
> attached patch and new files placed as usual. I did a bunch of gross
^^^6
> hacks he
On Wed, Jan 19, 2005 at 10:12:25AM +, Angus Leeming wrote:
> Angus Leeming wrote:
>
> > I've been trying out the signal handler on Windows. Executive summary:
> > SIGFPE and SIGSEGV are handled properly. The other signals are
> > essentially useless on Windows machines. However, the Windows ta
On Thu, Jan 20, 2005 at 09:59:20AM +0100, Lars Gullik Bjønnes wrote:
> Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
>
> | If any of you twits had bothered to look, you would see that the
> | second patch actually changed the definitions, rather than the forward
> | declarations.
>
> :-)
>
> S
On Sat, Jan 22, 2005 at 03:30:44PM +0100, Asger Ottar Alstrup wrote:
> John Weiss wrote:
> >Doing true full-Windows support in an inherently-unix program is a
> >very thorny, messy situation.
>
> Have a look at the patch and then give your comments rather than this FUD.
Not FUD. Reality. Be fai
Hi Angus,
Here you are. I made the changes you suggested.
But probably there's still whitespace wrong, superflous includes,
symbols in the wrong namespace etc. -- just tell me.
I made a short test: a small file with some maths and then scrolling
thru Userguide.lyx
with PageDown, checking that th
On Sun, Jan 23, 2005 at 10:44:08PM +, Angus Leeming wrote:
> Andreas Vox wrote:
> > When I activate previews and then click on a previewed formula I get:
> >
> > Assertion triggered in void lyxbreaker(const void*, const char*,
> > int) by failing check "false" in file coordcache.C:20
>
>
On Mon, Jan 24, 2005 at 01:58:24PM +0100, Asger Ottar Alstrup wrote:
> Lars Gullik Bjønnes wrote:
> >Please figure on list.
>
> You're such a control freak.
Last time I saw him he was pretty much out of control of the sleigh he
was riding...
Andre'
> > What about filepaths with spaces on unices, then? IIRC they tend to break
> > LaTeX runs anyway, so maybe we don't care either?
>
> Ahhh. But MikTeX on Windows definitely does support spaces in file names.
> Moreover, since everything is copied to a temp directory for compilation
> and the file
Andreas Vox wrote:
> Sounds ok?
Yes. Welcome aboard ;-)
--
Angus
Hi!
Angus Leeming <[EMAIL PROTECTED]> writes:
>
It seems GMane ate my last post, so I try again.
And it doesn't like "top posting" -- or what it thinks it is.
> The diff file looks great. But it's hard to see in detail what's happening.
> Could you post the PreviewLoader.C file (yeah, I'm lazy)
So I tried this idea, if ~S-^would be recognized, but no.
What did help though was adding this to the X config:
Option "XkbVariant""nodeadkeys"
Now ^ for superscript works again... rejoice children of Israel...
Still, no accents by deadkeys, and not by compose either (I enabled the
Hi Jean-Marc,
I think there is a bug in the ./configure script of LyX 1.3.X (I haven't
checked 1.4.0).
According to
./configure --help
you are allowed to specify --with-pspell-lib and --with-pspell-include.
However, when you do so, nothing happens. Reason: Actually, configure
expect --with-psp
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
...
> Ldiff does some of that. It would be interesting to investigate how
> this could be included in LyX.
I had a look. Same idea but it works on the file level.
I wanted to polish my C++ and STL knowledge, so I thought
it would be more intere
Kuba Ober wrote:
>> >>> But you argue that is it not really a problem for what we are
>> >>> doing, right? What about spaces in paths?
>> >
>> > Angus> Screws things up.
>> >
>> > Is that a problem in practice? (do we encounter this case in 1.3.x?)
>>
>> We have never had any official Windows user
> >>> But you argue that is it not really a problem for what we are
> >>> doing, right? What about spaces in paths?
> >
> > Angus> Screws things up.
> >
> > Is that a problem in practice? (do we encounter this case in 1.3.x?)
>
> We have never had any official Windows users to date.
What about fi
The attached program compiles perfectly when compiled against the LyX 1.3.x
and 1.4.x versions of Boost, but segfaults when the 1.4.x version is run.
At least, it does here
I don't think that this is too controversial, is it?
int main()
{
boost::signal sig;
return 0;
}
This is with the F
Angus Leeming wrote:
> Oh, if the file is meant to change only at predetermined times, then a
> single line added to lyx_cb.C's Reconfigure would do the trick:
>
> LatexFeatures::getAvailable();
>
> no?
Ah, yes, probably. Maybe I'll have a look after my return (weekend).
Regards,
Jürgen
Rob Lahaye wrote:
>
> My LyX, by default, uses for Postscript viewing "gv -swap"
> (as in Tools->Preferences->Conversion->Formats, Postscript)
>
> However, eversince I upgraded to gv version 3.6.1, the -swap does
> not work anymore, and consequently, Postscript viewing with LyX is
> not working (n
Jean-Marc Lasgouttes wrote:
>> "Angus" == Angus Leeming <[EMAIL PROTECTED]>
>> writes:
>
> Angus> Jean-Marc Lasgouttes wrote: Jean-Marc Lasgouttes wrote:
> What I was not sure about is how you handle option=='foo bar'.
>>>
> Angus> We don't. All hell breaks loose at this point and alw
Juergen Spitzmueller wrote:
> Angus Leeming wrote:
>> What you could do is "watch" packages.lst and read it again when it
>> changes. See RenderMonitoredPreview (src/insets/render_preview.[Ch]).
>>
>> Basically, you'd store a
>> // Check the file every 2 secs
>> lyx::support::FileMonitor monitor_(
Angus Leeming wrote:
> What you could do is "watch" packages.lst and read it again when it
> changes. See RenderMonitoredPreview (src/insets/render_preview.[Ch]).
>
> Basically, you'd store a
> // Check the file every 2 secs
> lyx::support::FileMonitor monitor_(std::string(), 2000);
>
> Onc
Juergen Spitzmueller wrote:
> Angus Leeming wrote:
>> ..and what's a PackagesList? Is the compiler looking for
>>
>> LaTeXFeatures::PackagesList LaTeXFeatures::packages_;
>>
>> perhaps?
>
> Umm. Thank you both.
> The static list works now. The only drawback (vs. non-static) is that you
> have to
Jean-Marc Lasgouttes wrote:
> Rob> It's because of both, _GLIBCXX_DEBUG and _GLIBCXX_DEBUG_PEDANTIC.
>
> Rob> Does that make sense?
>
> So the stdlibc++ debug feature is broken with your compiler version, I
> guess. You should ask the freebsd people for more info. When we know
> exactly what happen
Angus Leeming wrote:
> ..and what's a PackagesList? Is the compiler looking for
>
> LaTeXFeatures::PackagesList LaTeXFeatures::packages_;
>
> perhaps?
Umm. Thank you both.
The static list works now. The only drawback (vs. non-static) is that you have
to restart LyX to get packages.lst reparse
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc Lasgouttes wrote: Jean-Marc Lasgouttes wrote:
What I was not sure about is how you handle option=='foo bar'.
>>
Angus> We don't. All hell breaks loose at this point and always has.
>> But you argue that is it not rea
> "Rob" == Rob Lahaye <[EMAIL PROTECTED]> writes:
>> It seems that at least one of these is broken. If you have time,
>> you could try to turn them off one by one and see which one is the
>> culprit.
Rob> It's because of both, _GLIBCXX_DEBUG and _GLIBCXX_DEBUG_PEDANTIC.
Rob> Does that make s
Hi,
My LyX, by default, uses for Postscript viewing "gv -swap"
(as in Tools->Preferences->Conversion->Formats, Postscript)
However, eversince I upgraded to gv version 3.6.1, the -swap does
not work anymore, and consequently, Postscript viewing with LyX is
not working (not working with out-of-th
Juergen Spitzmueller wrote:
> * format incremented to 240.
> * new bufferparam:
> \output_changes {true|false}
> (should the change tracking marks be visible in the output or not?)
> * lyx2lyx should just delete the param in 239.
Here is the patch. Untested, but should work ;-)
Georg? output_ch
Juergen Spitzmueller wrote:
> I might be totally blind, but I cannot get it to compile.
...and what's a PackagesList? Is the compiler looking for
LaTeXFeatures::PackagesList LaTeXFeatures::packages_;
perhaps?
--
Angus
Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> Please figure on list.
>
| You're such a control freak.
No. I am an information freak. I want to know what happens.
| You can have some faith in me. Things propresses so much faster that
| way. If you trust me to do
Hartmut Haase wrote:
> Hi Jean-Marc,
> after todays update I configured with
> ./configure --with-frontend=qt --with-version-suffix=-latestcvs
> and got the the following error messages for make:
>
> Making all in client
> make[3]: Entering directory `/home/haase/Software/lyx-devel/src/client'
>
Juergen Spitzmueller wrote:
>> PackagesList LaTeXFeatures::packages_;
Try
LaTeXFeatures::PackagesList LaTeXFeatures::packages_;
because PackagesList is a type defined inside the class LaTeXFeatures.
Georg
Georg Baum <[EMAIL PROTECTED]> writes:
| Angus Leeming wrote:
>
>> Putting that to one side, we really, really should try and get LyX 1.4.0
>> out of the door. Lars announced some sort of feature freeze several months
>
| Yes please
Consider us in bug fixes only mode then (I only want the res
Jean-Marc Lasgouttes wrote:
>> Rob Lahaye writes:
>
> Rob> Yep, that solves the problem; not that I know what I'm doing
> Rob> though. But LyX compiles like a charm!
>
> Rob> Can you explain a little? Is this a bug, or a misbehaving feature
> Rob> of FreeBSD, or perhaps LyX or gcc?
>
> I think
Hi Jean-Marc,
after todays update I configured with
./configure --with-frontend=qt --with-version-suffix=-latestcvs
and got the the following error messages for make:
Making all in client
make[3]: Entering directory `/home/haase/Software/lyx-devel/src/client'
if g++ -DHAVE_CONFIG_H -I. -I. -I../
Angus Leeming wrote:
> It isn't static in the patch you posted.
Sure isn't ;-)
> Anyway, this is what you need:
>
> LaTeXFeatures.h
>
> class LaTeXFeatures {
> ...
> static PackagesList packages_;
> };
>
> LaTeXFeatures.C (immediately below the #includes):
>
> PackagesList LaTeXFeatures
On Mon, 2005-01-24 at 14:22, Martin Vermeer wrote:
> Noteworthy is that
>
> - my LyX thinks that I pressed the key combination [S-^], which it does
> not recognise as anything that should trigger math-superscript, or
> anything else for that matter; whereas
> - your LyX thinks you pressed [S-as
Georg Baum wrote:
> I can do that this evening if I know what you wrote in development/FORMAT.
> I guess it is only the new parameter in the header?
Yes. Here's what I wrote:
* format incremented to 240.
* new bufferparam:
\output_changes {true|false}
(sho
Jean-Marc Lasgouttes wrote:
> Angus> Jean-Marc Lasgouttes wrote:
>>> What I was not sure about is how you handle option=='foo bar'.
>
> Angus> We don't. All hell breaks loose at this point and always has.
>
> But you argue that is it not really a problem for what we are doing,
> right? What about
Rob Lahaye wrote:
> I start LyX-cvs like this:
> $ src/lyx -userdir /tmp/LyX
>
> Because /tmp/LyX does not exist, a dialog appears with
>
> You have specified a non-existent user LyX
> directory, /tmp/LyX.
> It is needed to keep your own configuration.
> [Creat
Angus Leeming wrote:
> Putting that to one side, we really, really should try and get LyX 1.4.0
> out of the door. Lars announced some sort of feature freeze several months
Yes please
> So, really, I think that your "green" decision should become:
>
> make a patch and post it to the list as
Hi,
I start LyX-cvs like this:
$ src/lyx -userdir /tmp/LyX
Because /tmp/LyX does not exist, a dialog appears with
You have specified a non-existent user LyX
directory, /tmp/LyX.
It is needed to keep your own configuration.
[Create directory][
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc Lasgouttes wrote:
>> What I was not sure about is how you handle option=='foo bar'.
Angus> We don't. All hell breaks loose at this point and always has.
But you argue that is it not really a problem for what we are doing
Juergen Spitzmueller wrote:
> Jean-Marc Lasgouttes wrote:
>> When you do that
>> -int const LYX_FORMAT = 239;
>> +int const LYX_FORMAT = 240;
>> don't forget to update development/FORMAT
>
> Sure (already done). I'll need someone to adapt lyx2lyx, though.
I can do that this evening if I know wha
> "Rob" == Rob Lahaye <[EMAIL PROTECTED]> writes:
Rob> Yep, that solves the problem; not that I know what I'm doing
Rob> though. But LyX compiles like a charm!
Rob> Can you explain a little? Is this a bug, or a misbehaving feature
Rob> of FreeBSD, or perhaps LyX or gcc?
I think this is a bug
Jean-Marc Lasgouttes wrote:
> What I was not sure about is how you handle option=='foo bar'.
We don't. All hell breaks loose at this point and always has. The existing
code to split a string up into an argv array is:
char *argv[MAX_ARGV];
string line = command_;
int index = 0;
fo
Jean-Marc Lasgouttes wrote:
>>"Rob" == Rob Lahaye <[EMAIL PROTECTED]> writes:
>
>
> Rob> I can compile LyX almost; something goes wrong at the very end.
> Rob> At the end of gmake, when the final executable is being linked, I
> Rob> get zillions of following lines:
>
> Rob> $ gmake [...]
> Rob
Asger Ottar Alstrup wrote:
> May I propose the following code of operation:
> - Red decisions:
> - Yellow decisions:
> - Green decisions:
That's the way that I generally operate, but I often have my wrists slapped
too. If course, you're probably more proficient than me, so you may well
receive les
Jean-Marc Lasgouttes wrote:
> When you do that
> -int const LYX_FORMAT = 239;
> +int const LYX_FORMAT = 240;
> don't forget to update development/FORMAT
Sure (already done). I'll need someone to adapt lyx2lyx, though.
Jürgen
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> It's not meant to be hard. It does this:
Angus> Store the input string "exe option option option" as a
Angus> vector
Angus> Convert all spaces ' ' to '\0'
What I was not sure about is how you handle option=='foo bar'.
Angus> To
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Done. Updated patch (without the getAvailable() changes)
Juergen> attached.
When you do that
-int const LYX_FORMAT = 239;
+int const LYX_FORMAT = 240;
don't forget to update development/FORMAT
JMarc
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> It isn't static in the patch you posted. Anyway, this is what
Angus> you need:
Angus> LaTeXFeatures.h
Angus> class LaTeXFeatures { ... static PackagesList packages_; };
Angus> LaTeXFeatures.C (immediately below the #includes):
A
On Monday 24 January 2005 09:51, Martin Vermeer wrote:
>
> Yes, agree. But it is packaged in qt with FC3.
The packages from kde-redat.se.net don't have that problem. :-)
Since I saw you use rpmforge you can also use kde-redhat packages. :-)
> - Martin
--
Josà AbÃlio
Lars Gullik Bjønnes wrote:
Please figure on list.
You're such a control freak.
You can have some faith in me. Things propresses so much faster that
way. If you trust me to do the right thing, and that I'll correct any
mistakes I make, life is simpler and progress faster.
I understand that this r
Juergen Spitzmueller wrote:
>> I am not sure putting this list in LaTeXFeatures like that is the best
>> solution, since packages.lst will be parsed everytime one exports to
>> latex... You may want to turn packages_ into a static variable and
>> make getPackage static too.
>
> I tried this, but t
Jean-Marc Lasgouttes wrote:
> > "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> The patch looks good. A few remarks:
>
> + case LFUN_OUTPUT_CHANGES: {
> + LaTeXFeatures features(*buf, buf->params(), false);
> + if (!features.isAvailable("dvipost"))
>
Am Freitag, 21. Januar 2005 14:11 schrieben Sie:
> Hartmut Haase wrote:
> > > > I was not aware of this.
> > > >
> > > > With filled math-bullet I mean \bullet in contrast to \circ
> > >
> > > I see. But I cannot reproduce the problem neither in 1.3.6cvs nor in
> > > 1.4cvs.
> >
> > Well, I use qt,
On Mon, 2005-01-24 at 13:26, Angus Leeming wrote:
> On Monday 24 January 2005 10:56, Martin Vermeer wrote:
...
> > Any other difference you can think of? What does lyx -dbg key say
> > for ^ ?
>
> Attached is the output of
> $ qlyx13x -dbg key > dbg.log 2>&1
>
> in which I:
> HTH,
> Angus
I t
Jean-Marc Lasgouttes wrote:
> I have taken a look at it, and it seems fine to me. I have to admit I
> have problems understanding Forkedcall::generateChild, but I trust
> your carefulness (?).
It's not meant to be hard. It does this:
Store the input string
"exe option option option"
as a vect
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> * I have one other patch for the 1.3.x tree that I have also
Angus> posted earlier and so am not attaching here,
Angus> placeholders_13x.diff: Define converters as "python
Angus> $$s/scripts/lyxpreview2ppm.py"
Angus> Jean-Marc has
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc has stated at various occassions that all of the
Angus> above were fine to apply to the 1.3.x tree. I was just waiting
Angus> for the problems Kayvan was having with LyX 1.4.x to be
Angus> resolved. That now seems to be th
This is just a status report. No action needed ;-)
I have two patches for the 1.3.x tree:
* The attached patch is just a re-packaging of a number of other, smaller
patches that I've posted to the list before. I describe these again below.
* I have one other patch for the 1.3.x tree that I have a
On Monday 24 January 2005 10:56, Martin Vermeer wrote:
> (To make sure: you type ^ and a blue superscript box opens?
Yes.
> What keyboard do you have and is ^ supposed to be a deadkey on it?)
A generic 105 key keyboard. Attached is my /etc/X11/xorg.conf file.
> Weird. Has anything changed here
On Mon, 2005-01-24 at 12:14, Angus Leeming wrote:
> On Monday 24 January 2005 10:01, Martin Vermeer wrote:
> > > Mine do *partially*. They work in KDE apps like this knode
> > > console, but not when I'm using LyX. And again, I emphasise that
> > > I'm using the compose-key approach to write accent
Jean-Marc Lasgouttes wrote:
> Angus> Are you happy for me to simply commit the above change to both
> Angus> the 14x and 13x trees?
>
> Sure, go ahead. I have not forgotten that I should fix this, but have
> other work waiting for me...
Of course.
--
Angus
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc, when I was testing whether the extra mkinstalldirs
Angus> was needed, I first modified my local versions of
Angus> config/relyx_configure.{ac,in}, so:
Angus> -# make sure prefix is correctly quoted -prefix="'$prefix'"
A
Lars Gullik Bjønnes wrote:
> | Lars Gullik Bjønnes wrote:
>>> Sure it is nice to compile on more than one compiler... but if the
>>> result is muddier code then I am not sure about the gain. (and not
>>> that I have not said that this is the case, just a thing to watch out
>>> for. and we already s
On Monday 24 January 2005 10:01, Martin Vermeer wrote:
> > Mine do *partially*. They work in KDE apps like this knode
> > console, but not when I'm using LyX. And again, I emphasise that
> > I'm using the compose-key approach to write accents. I have no
> > real idea what dead keys are but have thi
On Mon, 2005-01-24 at 10:30, Angus Leeming wrote:
> Martin Vermeer wrote:
> > No, rather not. Have them too already :-(
> > My version is qt-3.3.3-8.
>
> Mine too.
>
> > So, you seem to have the same stuff as I, but your accents work and mine
> > don't.
>
> Mine do *partially*. They work in KDE
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> Sure it is nice to compile on more than one compiler... but if the
>> result is muddier code then I am not sure about the gain. (and not
>> that I have not said that this is the case, just a thing to watch out
>> for. and we
On Mon, 2005-01-24 at 10:46, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> Just wanted to report that under FC3, LyX isn't able to use
> Martin> dead keys like ' ` ^ and the like. Also in math, ^ doesn't
> Martin> produce a superscript. Anno
> "Rob" == Rob Lahaye <[EMAIL PROTECTED]> writes:
Rob> I can compile LyX almost; something goes wrong at the very end.
Rob> At the end of gmake, when the final executable is being linked, I
Rob> get zillions of following lines:
Rob> $ gmake [...]
Rob>
BranchList.o(.gnu.linkonce.t._ZN10__gnu_
Lars Gullik Bjønnes wrote:
> Sure it is nice to compile on more than one compiler... but if the
> result is muddier code then I am not sure about the gain. (and not
> that I have not said that this is the case, just a thing to watch out
> for. and we already see quite a bit of preprocessors tokens
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> The attached patch fixes some real problems with the output
Juergen> of change tracked documents and implements a possibility to
Juergen> check whether a (required) package is installed.
Good idea.
Juergen> - If dvipost
Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
| Hi,
>
| Attached is a screen shot of the LyX start up with the MSVC compiled
| version.
>
| The patch is there as well.
>
| Remaining:
>
| - Get the last files remaining. At least, I need a lyxrc.defaults file.
>
| - Implement the stuff stubbed out
On Friday 21 January 2005 16:14, Angus Leeming wrote:
> >
> > Which one shall I implement?
>
> Option 1, Definitely. Without question.
I agree.
--
José Abílio
Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> I thought you said that files like this were not needed...
>
| They are not needed, but they are useful. It turns out that signals
| and regex boost libraries automatically add a linking request in the
| source code wi
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Tue, Jan 18, 2005 at 07:36:36AM -0500, John Weiss wrote:
>> On Mon, Jan 17, 2005 at 02:09:33PM +0100, Lars Gullik Bjønnes wrote:
>> >
>> > I feel we are beginning on a slippery slope now... ok to support
>> > windows if only minimal changes are neede
Jean-Marc,
when I was testing whether the extra mkinstalldirs was needed, I first
modified my local versions of config/relyx_configure.{ac,in}, so:
-# make sure prefix is correctly quoted
-prefix="'$prefix'"
I did this because I found that setting the prefix explicitly leads to the
creation of t
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> Just wanted to report that under FC3, LyX isn't able to use
Martin> dead keys like ' ` ^ and the like. Also in math, ^ doesn't
Martin> produce a superscript. Annoying.
Martin> It's a qt-3.3.3- bug known as 141475 by Red Hat's
Ma
> "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes:
Andreas> Hi! Wouldn't it be nice if LyX had the function "Compare
Andreas> document" as in OpenOffice?
Sure.
Andreas> As I understand it, the change tracking function only records
Andreas> changes as they are done. With this function, yo
Martin Vermeer wrote:
> No, rather not. Have them too already :-(
> My version is qt-3.3.3-8.
Mine too.
> So, you seem to have the same stuff as I, but your accents work and mine
> don't.
Mine do *partially*. They work in KDE apps like this knode console, but not
when I'm using LyX. And again, I
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I can confirm that everything worked as expected, so I think
Angus> that we can remove the mkinstalldirs in the top-level
Angus> directory.
Angus> OK?
Yes.
JMarc
86 matches
Mail list logo
