Dear all,
686 has driven me nuts! I may submit a very simple patch, instead of
trying to fix the whole del/bs scenario.
In the meantime, for your amusement, attached is a small patch that
adds lyx revision number to the about box. This is a quick hack and I
have not though about the whole autogen
>>Note that if CJK-LyX takes use the fact that wchar_t is 32 bit on
>>linux, then it won't work on windows sine wchar_t is only 16 bit there.
>>
>>--
>>Lgb
Since qt handles wchar_t well in Linux, why not in Windows?
Regards,
cghan
> Have you fixed J-M concerns about this patch?
Yes. That has been fixed. A painful python regex to boost::regex has been used.
> You are not allowed to use trunk as a place to store your unfinished
> patches/features you know...
This patch is by itself complete. It allows users to open .lyx fil
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
| - Original Message -
| >> From: "Wang Xiangqi" <[EMAIL PROTECTED]>
| >> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
| >> Date: 2006-04-08 21:25:00
| >> Subject: Re: CJK-LyX-1.4.0 (release-2)
| >>
| >> Windows version can be compiled for us
[EMAIL PROTECTED] writes:
| Author: bpeng
| Date: Sun Apr 9 06:35:24 2006
| New Revision: 13611
|
| Log:
| First patch for auto-cls-layout feature, from Bo Peng ([EMAIL PROTECTED])
| layout file in the same directory as .lyx file will be used. .cls can
also
| be in this directory.
- Original Message -
>> From: "Wang Xiangqi" <[EMAIL PROTECTED]>
>> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>> Date: 2006-04-08 21:25:00
>> Subject: Re: CJK-LyX-1.4.0 (release-2)
>>
>> Windows version can be compiled for users' convienience?
>> Thanks
>>
I do not use Windows in my
> Or to not specify any specific font, but just ask for the guis
> typewriter font. But hardcoding as it is not is not nice.
I am a total qt newbie and the dialog part is copied from QLog. Can
anyone tell me exactly how to "tell gui use typewriter font', if it is
on the top of your mind?
> | Defi
"Bo Peng" <[EMAIL PROTECTED]> writes:
| Finally...
|
| > |+void Buffer::getSourceCode(ostream& os, lyx::pit_type par_begin,
lyx::pit_type par_end)
| > |+{
| >
| > space before (and after) '&' please (same for '*')
| > (I see that you are not quite consistent)
|
| Yes. Have double-checked, but
Finally...
> |+void Buffer::getSourceCode(ostream& os, lyx::pit_type par_begin,
> lyx::pit_type par_end)
> |+{
>
> space before (and after) '&' please (same for '*')
> (I see that you are not quite consistent)
Yes. Have double-checked, but ...
> |+ // this is personal. I think source cod
[EMAIL PROTECTED] writes:
| Author: bpeng
| Date: Sun Apr 9 04:48:54 2006
| New Revision: 13610
|
| Log:
| view-source feature, from Bo Peng <[EMAIL PROTECTED]>
| * src/buffer.h buffer.C - getSourceCode()
|Index: src/buffer.C
|=
On Sat, Apr 08, 2006 at 01:40:44PM +, Angus Leeming wrote:
> john <[EMAIL PROTECTED]> writes:
> > Hi, I noticed that in LaTeX I can cite "BaToTr" or "batotr", either will
> > work. However, if I try to cite both in the same master document, e.g.
> > \citep{BaToTr}
> > \citep{batotr}
> > Then th
On Sat, 8 Apr 2006, Jose' Matos wrote:
> > http://wiki.lyx.org/LyX/LyXVersionNumbers
> > Should I let it stay on the users' wiki, should it be moved to the
> > developers' wiki or simply removed (i.e. is it redundant)?
>
> I like, but then I am suspect (for some reason that I have convenie
Am Samstag, 8. April 2006 20:57 schrieb Abdelrazak Younes:
> OK, here's the patch. Please verify that I did not any mistake in
> Makefile.am.
> This patch removes the hack for now by using LibFileSearch as you
> suggested. I like very much the qrc approach suggested by Andre but I
> think this s
"Bo Peng" <[EMAIL PROTECTED]> writes:
| Dear all,
|
| I check out a fresh lyx trunk, apply my patch, compile. A 'svn diff'
| gets me lots of po file changes. Can they be safely committed like
| this? Or should I clean them and commit only my patch? (rm -rf po, svn
| update; svn commit) Sorry if
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Enrico Forestieri a écrit :
| > On Sat, Apr 08, 2006 at 07:00:01PM +0200, Abdelrazak Younes wrote:
| >
| >> Enrico Forestieri a écrit :
| >>> All the necessary machinery to activate it is already present in
| >>> configure and configure.py, so this s
"Bo Peng" <[EMAIL PROTECTED]> writes:
| > - you obey the general coding/formatting rules.
|
| In general, I am. I would suggest again that we use a beautifier with
| one agreed set of parameters.
I have failed to find one, but sure if you can find a tool then please
use that.
--
Lgb
On Sat, Apr 08, 2006 at 09:52:53PM +0200, Abdelrazak Younes wrote:
> Enrico Forestieri a écrit :
> > On Sat, Apr 08, 2006 at 07:00:01PM +0200, Abdelrazak Younes wrote:
> >
> >> Enrico Forestieri a écrit :
> >>> All the necessary machinery to activate it is already present in
> >>> configure and c
On Sat, Apr 08, 2006 at 09:45:21PM +0200, Georg Baum wrote:
> Am Samstag, 8. April 2006 18:14 schrieb Enrico Forestieri:
> > All the necessary machinery to activate it is already present in
> > configure and configure.py, so this simple patch to os_win32.C
> > allows using the cygwin tetex with a
Dear all,
I check out a fresh lyx trunk, apply my patch, compile. A 'svn diff'
gets me lots of po file changes. Can they be safely committed like
this? Or should I clean them and commit only my patch? (rm -rf po, svn
update; svn commit) Sorry if I am asking something really basic.
Cheers,
Bo
On Sat, Apr 08, 2006 at 03:27:44PM -0500, Bo Peng wrote:
> > Attached my next attempt. Now,
>
> pullArg is used at some other places (font something?) Are you sure
> your pullArg will work over there?
I tried with fontinsets in math, i.e., \textrm. Seems to work. (And
looking at the code, I suspe
On Saturday 08 April 2006 14:00, [EMAIL PROTECTED] wrote:
> I read a post by Jose' in the user's list and started thinking about
> version numbers used by LyX. Eventually I tried explaining it to
> myself and wrote it down here:
>
> http://wiki.lyx.org/LyX/LyXVersionNumbers
>
> I've pasted th
> IMO the following procedure would be OK:
Taking the example of the view-source patch,
> If there is agreement about a particular feature,
Yes.
> and also about the
> general implementation (I don't mean the details, but the overall
> approach),
No. The patch is a little big. It has been a li
> Attached my next attempt. Now,
pullArg is used at some other places (font something?) Are you sure
your pullArg will work over there?
Bo
Georg Baum a écrit :
Am Samstag, 8. April 2006 17:45 schrieb Bo Peng:
What I need from you, more experienced lyx developers, is a quick look
at the patch, find logic errors (like JMarc did for my auto-cls-layout
patch), design flaws (like the bundling of lastfile with lastpos), or
better implem
> You're right, it is not a simple check. Should
> probably be renamed to "trySimpleLabelUpdate".
> Opinion?
separate the check and the labelupdate?
do updatecounters and updatelabel always coincide?
am not the person to answer really
Leuven, E. a écrit :
>> what happens in setCounter(,)?
> It is misnamed (should be setLabel, I am working on that).
> This would set the bullet depending on the depth of the
> current paragraph.
i don't understand why anything needs to be 'set' if we are only
checking whether something need
Enrico Forestieri a écrit :
On Sat, Apr 08, 2006 at 07:00:01PM +0200, Abdelrazak Younes wrote:
Enrico Forestieri a écrit :
All the necessary machinery to activate it is already present in
configure and configure.py, so this simple patch to os_win32.C
allows using the cygwin tetex with a native
Title: RE: Re: feature request
>> what happens in setCounter(,)?
> It is misnamed (should be setLabel, I am working on that).
> This would set the bullet depending on the depth of the
> current paragraph.
i don't understand why anything needs to be 'set' if we are only checking whether some
Am Samstag, 8. April 2006 17:19 schrieb Bo Peng:
> >
> > > 1. del at [abc|] work as backspace (instead of doing nothing)
> >
> > No, should melt the inset's content into the surrounding ite,
>
> What exact do you mean? It sounds dangerous and difficult to 'melt the
content'.
This is something
On Sat, Apr 08, 2006 at 09:12:35AM +0300, Martin Vermeer wrote:
> On Fri, Apr 07, 2006 at 11:17:05PM +0200, Abdelrazak Younes wrote:
> > Martin Vermeer a écrit :
> > >...from the math panel.
...
> The fix for this is to remove the LFUN_UP, LFUN_DOWN calls in
> ControlMath.C. I will commit this f
Am Samstag, 8. April 2006 18:14 schrieb Enrico Forestieri:
> All the necessary machinery to activate it is already present in
> configure and configure.py, so this simple patch to os_win32.C
> allows using the cygwin tetex with a native win32 LyX.
>
> Log:
> * src/support/os_win32.C: activat
Leuven, E. a écrit :
Use needsUpdateCounters. See text2.C for example.
i had a look at it and was wondering about the following
case LABEL_ITEMIZE:
setCounter(buf, it);
return false;
what happens in setCounter(,)?
It is misnamed (should be setLabel,
> Use needsUpdateCounters. See text2.C for example.
i had a look at it and was wondering about the following
case LABEL_ITEMIZE:
setCounter(buf, it);
return false;
what happens in setCounter(,)? if needsUpdateCounters() only *checks* for the
type of layo
Am Samstag, 8. April 2006 20:40 schrieb Bo Peng:
> With /branches/bpeng, nobody will check it out and test, except maybe
> you, because there are *too many* such branches.
Do you know svn switch?
> With /sandbox or
> /next, all potential patches go here and people can play with it and
> test all
On Fri, Apr 07, 2006 at 04:59:37PM -0500, Bo Peng wrote:
> > > What do you think?
>
> I see the only difference: I move the cursor left in the case of
>
> [|]
> ---
> [abc]
>
> but you don't. My patch is compatible with the current behavior.
Ah yes. Actually nothing happening when you press a k
Am Samstag, 8. April 2006 17:45 schrieb Bo Peng:
> What I need from you, more experienced lyx developers, is a quick look
> at the patch, find logic errors (like JMarc did for my auto-cls-layout
> patch), design flaws (like the bundling of lastfile with lastpos), or
> better implementations.
This
Jose' Matos a écrit :
On Saturday 08 April 2006 19:31, Angus Leeming wrote:
You can already do that: branches/abdel/
You don't need permission, just set it up and ask Edwin to check it out ;-)
Clearly the point, what we need is another Andrew Morton. And you (Abdel)
are welcome be that guy
Georg Baum a écrit :
Am Freitag, 7. April 2006 23:56 schrieb Georg Baum:
Here is the patch (again only the relevant files). It goes in tomorrow
if
nobody objects.
Done. Abdel, please fix the qt4 icons: Either by creating a resource file,
or by loading them at runtime and move the icons into
On Sat, Apr 08, 2006 at 07:49:32PM +0200, Leuven, E. wrote:
...
> > updateCounters(cur.buffer()); (2x)
> >
> > Please put a FIXME in here for Abdel (or fix yourself).
> > This will be dog slow on Windows.
>
> can i check whether a paragraph contains a counter (so that
> we updateCounters
Angus Leeming a écrit :
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
I have to improve my English as you don't seem to understand me. I am
talking about an easier way to improve a patch in a public way instead
of sending back and forth the updated patch. When the patch meets your
personal qua
> You can already do that: branches/abdel/
Why communication becomes so difficult now?
With /branches/bpeng, nobody will check it out and test, except maybe
you, because there are *too many* such branches. With /sandbox or
/next, all potential patches go here and people can play with it and
test
On Saturday 08 April 2006 19:31, Angus Leeming wrote:
> You can already do that: branches/abdel/
>
> You don't need permission, just set it up and ask Edwin to check it out ;-)
Clearly the point, what we need is another Andrew Morton. And you (Abdel)
are welcome be that guy. :-)
> Angus
--
J
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> I have to improve my English as you don't seem to understand me. I am
> talking about an easier way to improve a patch in a public way instead
> of sending back and forth the updated patch. When the patch meets your
> personal quality expectation t
Lars Gullik Bjønnes a écrit :
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes a écrit :
| > "Bo Peng" <[EMAIL PROTECTED]> writes:
| > | > There is always the branches/personal/* sub-tree, where you can
| > put
| > | > whatever.
| > | | But who will check out from there and te
Leuven, E. a écrit :
I'm sure you mean // 275 (is the count right?)
you're right!
updateCounters(cur.buffer()); (2x)
Please put a FIXME in here for Abdel (or fix yourself).
This will be dog slow on Windows.
can i check whether a paragraph contains a counter (so that
we updateCount
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes a écrit :
| > "Bo Peng" <[EMAIL PROTECTED]> writes:
| > | > There is always the branches/personal/* sub-tree, where you can
| > put
| > | > whatever.
| > | | But who will check out from there and test? My proposal was not
| > for
> I'm sure you mean // 275 (is the count right?)
you're right!
> updateCounters(cur.buffer()); (2x)
>
> Please put a FIXME in here for Abdel (or fix yourself).
> This will be dog slow on Windows.
can i check whether a paragraph contains a counter (so that
we updateCounters only when we n
On Sat, Apr 08, 2006 at 07:00:01PM +0200, Abdelrazak Younes wrote:
> Enrico Forestieri a écrit :
> > All the necessary machinery to activate it is already present in
> > configure and configure.py, so this simple patch to os_win32.C
> > allows using the cygwin tetex with a native win32 LyX.
>
> H
Georg Baum a écrit :
Am Freitag, 7. April 2006 18:11 schrieb Abdelrazak Younes:
Yes, as the icons path would be define in the action rc file: unified
menubar and toolbar with func definition, icons, tooltips, etc.
I see, but the current icon loading mechanism is not too bad (only the
automati
Lars Gullik Bjønnes a écrit :
"Bo Peng" <[EMAIL PROTECTED]> writes:
| > There is always the branches/personal/* sub-tree, where you can put
| > whatever.
|
| But who will check out from there and test? My proposal was not for
| commit, rather for easy testing for developers or even users.
Doi
Andre Poenitz a écrit :
On Fri, Apr 07, 2006 at 05:26:58PM +0200, Abdelrazak Younes wrote:
Andre Poenitz a écrit :
On Thu, Apr 06, 2006 at 01:52:35PM +0200, Abdelrazak Younes wrote:
Leuven, E. a écrit :
I think we can shortcut that by
using QLAction and avoid the call to
"form_->controller()
On 8 Apr 2006, Lars Gullik Bjønnes wrote:
> [EMAIL PROTECTED] writes:
>
> | `-- personal/
>
> |-- / - the user owning the banches therein
> ||-- / - eg testing/developing specific
> functions
>
> (not my added
Ok, so there should be a '/'/' ther
Enrico Forestieri a écrit :
All the necessary machinery to activate it is already present in
configure and configure.py, so this simple patch to os_win32.C
allows using the cygwin tetex with a native win32 LyX.
Hi Enrico,
Small question: if this patch was applied what would be missing in a
na
On Sat, Apr 08, 2006 at 06:14:36PM +0200, Enrico Forestieri wrote:
> All the necessary machinery to activate it is already present in
> configure and configure.py, so this simple patch to os_win32.C
> allows using the cygwin tetex with a native win32 LyX.
Ops... renamed dos_path to cygpath ;-)
-
All the necessary machinery to activate it is already present in
configure and configure.py, so this simple patch to os_win32.C
allows using the cygwin tetex with a native win32 LyX.
Log:
* src/support/os_win32.C: activate cygwin-tetex support
Do with it whatever you think fits better ;-)
+358,9 @@
LFUN_BIBDB_DEL,
LFUN_INSERT_CITATION,
LFUN_OUTLINE, // Vermeer 20060323
+ // ?
+ LFUN_MOVE_PARAGRAPH_DOWN,// Edwin 20060408
+ LFUN_MOVE_PARAGRAPH_UP, // Edwin 20060408
LFUN_LAST
"Leuven, E." <[EMAIL PROTECTED]> writes:
| sorry wrong file. correct patch here...
This looks good to me.
| Index: src/lfuns.h
| ===
| --- src/lfuns.h (revision 13594)
| +++ src/lfuns.h (working copy)
| @@ -358,6 +358,9
> Doing a switch to a different tree than trunk is for me somewhat
> easier than applying a patch. (At least sometimes)
But may not be easy for others, and is not making my life any easier.
I understand that it will make backporting a lot easier if a feature
is committed to the 1.5.x tree as a cor
Title: RE: Re: feature request
sorry wrong file. correct patch here...
Index: src/LyXAction.C
===
--- src/LyXAction.C (revision 13594)
+++ src/LyXAction.C (working copy)
@@ -353,6 +353,8 @@
{ LFUN_MOUSE_RELEASE, "", ReadO
>
> > 1. del at [abc|] work as backspace (instead of doing nothing)
>
> No, should melt the inset's content into the surrounding ite,
What exact do you mean? It sounds dangerous and difficult to 'melt the content'.
> > 2. backspace/del at [ [a] [|] [ ] ] moves to the end of first cell
>
> O
"Leuven, E." <[EMAIL PROTECTED]> writes:
| > Better, but perhaps to as J-M says and use
| > LFUN_PARAGRAPH_MOVE_{UP,DOWN} as well.
| > Can you have a quick look and see if there are
| > some nice place to put this in emacs.bind as well?
|
| updated patch attached
Are you going to do the LFUN ren
start = !par.params().startOfAppendix();
Index: src/lfuns.h
===
--- src/lfuns.h (revision 13594)
+++ src/lfuns.h (working copy)
@@ -358,6 +358,9 @@
LFUN_BIBDB_DEL,
LFUN_INSERT_CITATION,
LFUN_OUTLINE, // Vermeer 20060323
+ // ?
+ LFUN_MOVE
"Leuven, E." <[EMAIL PROTECTED]> writes:
| Index: src/LyXAction.C
| ===
| --- src/LyXAction.C (revision 13594)
| +++ src/LyXAction.C (working copy)
| @@ -353,6 +353,8 @@
| { LFUN_MOUSE_RELEASE, "", ReadOnly },
|
"Jean-Marc Lasgouttes" <[EMAIL PROTECTED]> writes:
| > Can we change the name of the LFUN?
|
| > MOVE_PARAGRAPH_{UP,DOWN}
|
| Rather paragraph-move-up.
|
| We use object-vverb order.
In the user visible text func names yes... i think that sevral of the
LFUN names do not follow this.
--
> Can we change the name of the LFUN?
> MOVE_PARAGRAPH_{UP,DOWN}
Rather paragraph-move-up.
We use object-vverb order.
JMarc
Georg Baum <[EMAIL PROTECTED]> writes:
>>>I think we should in general avoid to add new packages to LaTeXFeatures
>>>unless the already existing conflicts are solved and we have a more
>>flexible package loading mechanism. The more package syou load
>>>automatically, the more conflicts can arise.
Title: RE: Re: feature request
> Can we change the name of the LFUN?
done
> Note how you stole another commands name. (C-Up)
oops
like attached?
Index: src/LyXAction.C
===
--- src/LyXAction.C (revision 13594)
+++ src/LyX
[EMAIL PROTECTED] writes:
| > There is always the branches/personal/* sub-tree, where you can put
| > whatever.
|
| I didn't know about this... given that I just wrote something about the
| version numbers of LyX which related to branches, I wonder what else I
| don't know here...?
|
| If I un
"Leuven, E." <[EMAIL PROTECTED]> writes:
| > I think you could simply do ++cur.pit()/--cur.pit()
|
| works like a charm, updated patch attached.
|
| green light from the pundits?
Can we change the name of the LFUN?
MOVE_PARAGRAPH_{UP,DOWN}
I think I'l like to keep PARAGRAPH_{UP,DOWN} for curs
john <[EMAIL PROTECTED]> writes:
> Hi, I noticed that in LaTeX I can cite "BaToTr" or "batotr", either will
> work. However, if I try to cite both in the same master document, e.g.
> \citep{BaToTr}
> \citep{batotr}
> Then the second citation will be replaced with a "?".
That's the magic of LaTeX f
"Bo Peng" <[EMAIL PROTECTED]> writes:
| > There is always the branches/personal/* sub-tree, where you can put
| > whatever.
|
| But who will check out from there and test? My proposal was not for
| commit, rather for easy testing for developers or even users.
Doing a switch to a different tree t
"Jean-Marc Lasgouttes" <[EMAIL PROTECTED]> writes:
| > That is because we have used '#warning' as '#info'.
|
| Seeing how we ignore them, they should probably
| be replaced by plain FIXMEs.
Yes they should.
--
Lgb
On 8 Apr 2006, Lars Gullik Bjønnes wrote:
> "Bo Peng" <[EMAIL PROTECTED]> writes:
>
> | > I have proposed some days ago to have a "next" branch on SVN but noboby
> | > was interested apparently. Why don't you ask a SVN account and commit it
> | > yourself either in trunk if main devels are OK or
> Does your patch behave differently in that respect?
No. A newer version is trying to reverse empty undo, but it seems
that I have complicated the problem too much.
Bo
I read a post by Jose' in the user's list and started thinking about
version numbers used by LyX. Eventually I tried explaining it to
myself and wrote it down here:
http://wiki.lyx.org/LyX/LyXVersionNumbers
I've pasted the text below for convenience. Is the text correct? What
have I misse
> There is always the branches/personal/* sub-tree, where you can put
> whatever.
But who will check out from there and test? My proposal was not for
commit, rather for easy testing for developers or even users.
Bo
Hello,
I'm trying to become a new Lyx user, but...
I've installed Lyx 1.4.0 on a pretty fast dual Powermac G5 with
plenty of RAM and disk, together with MacTex.
It seems to work, but sounds horribly slow, and is unusable for me:
simply typing on the keyboard takes minutes to handle all the
Title: RE: feature request
> I think you could simply do ++cur.pit()/--cur.pit()
works like a charm, updated patch attached.
green light from the pundits?
edwin
Index: src/LyXAction.C
===
--- src/LyXAction.C (revision 1359
Hi, I noticed that in LaTeX I can cite "BaToTr" or "batotr", either will
work. However, if I try to cite both in the same master document, e.g.
\citep{BaToTr}
\citep{batotr}
Then the second citation will be replaced with a "?".
This can occur in LyX (e.g. 1.3.7) if you foolishly let bibtool mangle
Am Samstag, 8. April 2006 13:32 schrieb Leuven, E.:
> thanks for the hint. the attached seems to work (if feel like a child
with a gun when tinkering with the core ;-)
I know that feeling ;-) But not all parts of the core are dangerous.
> only puzzle that i could not solve is that the cursor is
Am Freitag, 7. April 2006 23:56 schrieb Georg Baum:
> Here is the patch (again only the relevant files). It goes in tomorrow
if
> nobody objects.
Done. Abdel, please fix the qt4 icons: Either by creating a resource file,
or by loading them at runtime and move the icons into the correct install
===
--- src/lfuns.h (revision 13594)
+++ src/lfuns.h (working copy)
@@ -358,6 +358,9 @@
LFUN_BIBDB_DEL,
LFUN_INSERT_CITATION,
LFUN_OUTLINE, // Vermeer 20060323
+ // ?
+ LFUN_PARAGRAPH_DOWN, // Edwin 20060408
+ LFUN_PARAGRAPH_UP,
> Can I suppose this '\\arabic{chapter}' will be replaced by a number?
Yes, exactly.
JMarc
> That is because we have used '#warning' as '#info'.
Seeing how we ignore them, they should probably
be replaced by plain FIXMEs.
JMarc
"Bo Peng" <[EMAIL PROTECTED]> writes:
| > I have proposed some days ago to have a "next" branch on SVN but noboby
| > was interested apparently. Why don't you ask a SVN account and commit it
| > yourself either in trunk if main devels are OK or in a new branch which
| > should be easy to create.
|
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Thu, Apr 06, 2006 at 09:34:01PM +0200, Lars Gullik Bjønnes wrote:
| > | I think some apache module comes with SVN which allows you to browse the
| > | repository. It's not very fancy though. Then there's also VievCV IIRC.
| >
| > I will upgrade the s
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| [EMAIL PROTECTED] a écrit :
| > > What if the compiler warning goes unnoticed? I really prefer to
| > use
| >> "default" in this case because by default it will do the full
| >> counter update.
| > We compile with all warnings enabled.
| > Ignoring
Hello Abdel,
I wasn't able to configure LyX, I got this error:
gcc version 3.4.4 (mingw special)
configure:3067: $? = 0
configure:3069: gcc -V &5
gcc.exe: `-V' option must have argument
configure:3072: $? = 1
configure:3095: checking for C compiler default output file name
configure:3098: gcc
Hi folks,
I've got few messages on fuzzy state, and they're the same.
msgid "Chapter \\arabic{chapter}"
Can I suppose this '\\arabic{chapter}' will be replaced by a number? I
mean:
Chapter 4
So in this case, in basque lang. should be (where 'atala' means
'chapter' in basque):
msgstr "\\arabic
Bo Peng wrote:
commandLine = malloc (commandLineLength);
commandLine = (char*)malloc (commandLineLength);
Many thanks for this. I works and I can now start MSYS.
regards Uwe
> The attached patch goes in right now. It fixes the bug for me, but not for
> Bennett. (I don't know
what happens in his case, but I know for sure what the problem is in my
> case and that this patch is the right fix.
You can apply it to branch too, since it has been
reported several times.
The attached patch goes in right now. It fixes the bug for me, but not for
Bennet (see http://bugzilla.lyx.org/show_bug.cgi?id=2231). I don't know
what happens in his case, but I know for sure what the problem is in my
case and that this patch is the right fix.
Georg
Log:
* src/insets/
On Fri, Apr 07, 2006 at 04:30:17PM +, Angus Leeming wrote:
> Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> > Yep, and what about creating a qt4 namespace? In due time
> > lyx::frontend::qt4::Action could inherit lyx::Action. Or is that against
> > your coding guidelines?
>
> Sounds good to
On Fri, Apr 07, 2006 at 05:26:58PM +0200, Abdelrazak Younes wrote:
> Andre Poenitz a écrit :
> >On Thu, Apr 06, 2006 at 01:52:35PM +0200, Abdelrazak Younes wrote:
> >>Leuven, E. a écrit :
> I think we can shortcut that by
> using QLAction and avoid the call to
> "form_->controller().d
On Thu, Apr 06, 2006 at 04:35:28PM -0500, Bo Peng wrote:
> 0. bug 686: del [|] remoes the whole inset, implemented
Ok.
> 1. del at [abc|] work as backspace (instead of doing nothing)
No, should melt the inset's content into the surrounding ite,
> 2. backspace/del at [ [a] [|] [ ] ] moves
On Fri, Apr 07, 2006 at 05:50:46PM +0200, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> | >> BTW, I am not too happy that we use a 'Q' prefix for _our_ Qt stuff.
> |
> | > Feel free to change that. I agree with with yo
96 matches
Mail list logo
