Am Sonntag, dem 13.02.2022 um 04:19 +0100 schrieb Thibaut Cuvelier:
> You mean, with code like
> https://github.com/cburschka/lyx/blob/d3c335a5d524e2edeb73ae1a891fcc58ba5bfd1a/src/BiblioInfo.cpp#L421-L428
> for the search? I thought it would be good to have a file to store
> this information, but I
e.asc
> Type: application/pgp-signature
> Size: 488 bytes
> Desc: This is a digitally signed message part
> URL: <
> http://lists.lyx.org/pipermail/lyx-cvs/attachments/20220209/980878f0/attachment-0001.asc
> >
>
You mean, with code like
https://github.com/cburschka/lyx/blo
Am Sun, 1 Mar 2020 11:02:28 -0500
schrieb Richard Kimberly Heck :
> On 3/1/20 10:55 AM, Kornel Benko wrote:
> > Renamig does not show in lyx-CVS
> > Your mail to 'lyx-cvs' with the subject
> >
> > [LyX/master] Moving 3rdparty/evince_sync to
> > 3r
On 3/1/20 10:55 AM, Kornel Benko wrote:
> Renamig does not show in lyx-CVS
> Your mail to 'lyx-cvs' with the subject
>
> [LyX/master] Moving 3rdparty/evince_sync to
> 3rdparty/scripts/evince_sync
>
> Is being held until the list moderator can review it for appro
Renamig does not show in lyx-CVS
Kornel
--- Begin Message ---
Your mail to 'lyx-cvs' with the subject
[LyX/master] Moving 3rdparty/evince_sync to
3rdparty/scripts/evince_sync
Is being held until the list moderator can review it for approval.
The reason it is
Am 10.01.2018 um 09:57 schrieb Pavel Sanda:
Change your git config, so your commiter name is not uwesto...@web.de but
uwesto...@lyx.org .
Many thanks Pavel. I did this now. I see that my lyx.org address is
already subscribed to lyx-cvs. I see that all mails from lyx-cvs are
automatically
Uwe Stöhr wrote:
> What do others do? I mean I don't like to get a mail for every commit since
Change your git config, so your commiter name is not uwesto...@web.de but
uwesto...@lyx.org .
https://help.github.com/articles/setting-your-commit-email-address-in-git/
Pavel
;m afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
>:
> Sorry, only subscribers may post. If you are a subscriber, please
> forward this message to lyx-cvs-ow...@lists.lyx.or
following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
:
Sorry, only subscribers may post. If you are a subscriber, please
forward this message to lyx-cvs-ow...@lists.lyx.org to get your new
address included.
I cannot remember that I had to be a subsc
On Tue, Jun 06, 2017 at 05:29:52PM -0400, Richard Heck wrote:
> I checked the last 1000 commits to 2.2.x, and setting the limit to 32000
> failed to send a complete commit log for only one commit for which you
> might want it: 54248a6e
The patch file for this commit is 34K in case someone was won
On 06/06/2017 05:04 PM, Richard Heck wrote:
> On 06/06/2017 03:35 PM, Scott Kostyshak wrote:
>> On Sun, Jun 04, 2017 at 10:58:52PM -0400, Richard Heck wrote:
>>> On 06/04/2017 09:02 PM, Scott Kostyshak wrote:
>>>> Commit 52eee8e5 ("Fix .po files") was n
On 06/06/2017 03:35 PM, Scott Kostyshak wrote:
> On Sun, Jun 04, 2017 at 10:58:52PM -0400, Richard Heck wrote:
>> On 06/04/2017 09:02 PM, Scott Kostyshak wrote:
>>> Commit 52eee8e5 ("Fix .po files") was not sent to lyx-cvs. I imagine it
>>> is because the
On Sun, Jun 04, 2017 at 10:58:52PM -0400, Richard Heck wrote:
> On 06/04/2017 09:02 PM, Scott Kostyshak wrote:
> > Commit 52eee8e5 ("Fix .po files") was not sent to lyx-cvs. I imagine it
> > is because the commit is 13MB. I think it is a good decision not to send
>
On 06/04/2017 09:02 PM, Scott Kostyshak wrote:
> Commit 52eee8e5 ("Fix .po files") was not sent to lyx-cvs. I imagine it
> is because the commit is 13MB. I think it is a good decision not to send
> patches that are too large, but it would be nice to receive at least the
>
Commit 52eee8e5 ("Fix .po files") was not sent to lyx-cvs. I imagine it
is because the commit is 13MB. I think it is a good decision not to send
patches that are too large, but it would be nice to receive at least the
commit message and the stats (which files were changed), and possibly
Am Freitag, 10. März 2017 um 19:26:12, schrieb Jean-Pierre Chrétien
> Le 10/03/2017 à 19:19, Jean-Pierre Chrétien a écrit :
>
> >
> > Just made a test to be sure, I pushed
> > * a quite small commit about AGUTeX.lyx
> > * a fresh update of fr.po and fr.gmo (however with only 3 changes this
Le 10/03/2017 à 19:19, Jean-Pierre Chrétien a écrit :
Just made a test to be sure, I pushed
* a quite small commit about AGUTeX.lyx
* a fresh update of fr.po and fr.gmo (however with only 3 changes this time,
instead of ~ a hundred the last time).
We'll see what mails lyx-devel will get fr
Le 10/03/2017 à 10:02, Kornel Benko a écrit :
Am Donnerstag, 9. März 2017 um 18:18:38, schrieb Pavel Sanda
IIRC we have some maximal size of mails which can get through our conferences.
Esp. with po/gmo changes those limits will be hit.
Pavel
Maybe, but consider that gmo-changes are not se
Am Donnerstag, 9. März 2017 um 18:18:38, schrieb Pavel Sanda
> Richard Heck wrote:
> > >> No. It may be that you are not whitelisted for posting to lyx-cvs.
> > >
> > > There have been posts from j...@lyx.org last month on lyx-cvs.
> >
> > Mystery,
Richard Heck wrote:
> >> No. It may be that you are not whitelisted for posting to lyx-cvs.
> >
> > There have been posts from j...@lyx.org last month on lyx-cvs.
>
> Mystery, then.
IIRC we have some maximal size of mails which can get through our conferences.
Esp
t; 7ca89e49, I did not see an acknowledgement on lyx-devel as usual.
>>> Is this a normal behaviour ?
>>
>> No. It may be that you are not whitelisted for posting to lyx-cvs.
>
> There have been posts from j...@lyx.org last month on lyx-cvs.
Mystery, then.
rh
that you are not whitelisted for posting to lyx-cvs.
There have been posts from j...@lyx.org last month on lyx-cvs.
JMarc
ted for posting to lyx-cvs.
I don't know how to deal with this, but I think JMarc does.
Richard
On Wed, Jun 22, 2016 at 02:16:06PM -0400, Richard Heck wrote:
> On 06/21/2016 07:48 PM, Scott Kostyshak wrote:
> > On Sat, Apr 16, 2016 at 01:43:18PM -0400, Scott Kostyshak wrote:
> >> On Sat, Apr 16, 2016 at 08:35:54AM -0400, Richard Heck wrote:
> >>> On 04/15/2016 05:45 PM, Scott Kostyshak wrote:
On 06/21/2016 07:48 PM, Scott Kostyshak wrote:
> On Sat, Apr 16, 2016 at 01:43:18PM -0400, Scott Kostyshak wrote:
>> On Sat, Apr 16, 2016 at 08:35:54AM -0400, Richard Heck wrote:
>>> On 04/15/2016 05:45 PM, Scott Kostyshak wrote:
On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote:
On Sat, Apr 16, 2016 at 01:43:18PM -0400, Scott Kostyshak wrote:
> On Sat, Apr 16, 2016 at 08:35:54AM -0400, Richard Heck wrote:
> > On 04/15/2016 05:45 PM, Scott Kostyshak wrote:
> > > On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote:
> > > > On Tue, Mar 29, 2016 at 10:49:55AM +0200
On Sat, Apr 16, 2016 at 08:35:54AM -0400, Richard Heck wrote:
> On 04/15/2016 05:45 PM, Scott Kostyshak wrote:
> > On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote:
> > > On Tue, Mar 29, 2016 at 10:49:55AM +0200, Jean-Marc Lasgouttes wrote:
> > > > Le 28/03/2016 00:04, Scott Kostysha
On 04/15/2016 05:45 PM, Scott Kostyshak wrote:
On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote:
On Tue, Mar 29, 2016 at 10:49:55AM +0200, Jean-Marc Lasgouttes wrote:
Le 28/03/2016 00:04, Scott Kostyshak a écrit :
It seems we currently use "git show ${hash}" in our script. Inste
On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote:
> On Tue, Mar 29, 2016 at 10:49:55AM +0200, Jean-Marc Lasgouttes wrote:
> > Le 28/03/2016 00:04, Scott Kostyshak a écrit :
> > >It seems we currently use "git show ${hash}" in our script. Instead of
> > >doing two commands like I naiv
On Tue, Mar 29, 2016 at 10:49:55AM +0200, Jean-Marc Lasgouttes wrote:
> Le 28/03/2016 00:04, Scott Kostyshak a écrit :
> >It seems we currently use "git show ${hash}" in our script. Instead of
> >doing two commands like I naively suggested above, what about the
> >following?
>
> What about "git sh
Le 28/03/2016 00:04, Scott Kostyshak a écrit :
It seems we currently use "git show ${hash}" in our script. Instead of
doing two commands like I naively suggested above, what about the
following?
What about "git show --stat"?
JMarc
On Mon, Feb 22, 2016 at 08:52:17PM +0100, Georg Baum wrote:
> Jean-Marc Lasgouttes wrote:
>
> > Le 18/02/2016 02:58, Scott Kostyshak a écrit :
> >> Would anyone else find it useful if the lyx-cvs messages showed the file
> >> names that were changed at the beginnin
Jean-Marc Lasgouttes wrote:
> Le 18/02/2016 02:58, Scott Kostyshak a écrit :
>> Would anyone else find it useful if the lyx-cvs messages showed the file
>> names that were changed at the beginning of a message? One example is
>> that I would often like to know if a commit is
Le 18/02/2016 02:58, Scott Kostyshak a écrit :
Would anyone else find it useful if the lyx-cvs messages showed the file
names that were changed at the beginning of a message? One example is
that I would often like to know if a commit is documentation only or if
there is another change that I
Would anyone else find it useful if the lyx-cvs messages showed the file
names that were changed at the beginning of a message? One example is
that I would often like to know if a commit is documentation only or if
there is another change that I would like to take a look at.
What I would
Neither Guillaume nor I have received emails regarding the last few
commits.
Scott
signature.asc
Description: PGP signature
is in /home/git/repositories/lyx.git/config.
Thanks. It is a bit difficult for me to understand what the code does,
though... Anyway, I propose that lyx-cvs just accepts all messages
coming from lyx.lyx.org. Would that be OK?
I think that would probably be fine, though if there is something
s. It is a bit difficult for me to understand what the code does,
though... Anyway, I propose that lyx-cvs just accepts all messages
coming from lyx.lyx.org. Would that be OK?
JMarc
On 10/19/2015 08:55 AM, Vincent van Ravesteijn wrote:
On Mon, Oct 19, 2015 at 1:38 PM, Jean-Marc Lasgouttes
wrote:
The title says it all. I'd like to add some header in there that the lyx-cvs
list can use to allow the message, instead of restricting to subscribers.
JMarc
It is in a git
On Mon, Oct 19, 2015 at 1:38 PM, Jean-Marc Lasgouttes
wrote:
>
> The title says it all. I'd like to add some header in there that the lyx-cvs
> list can use to allow the message, instead of restricting to subscribers.
>
> JMarc
It is in a git hook in a script called .git/h
The title says it all. I'd like to add some header in there that the
lyx-cvs list can use to allow the message, instead of restricting to
subscribers.
JMarc
On Saturday 11 July 2015 23:00:51 Guenter Milde wrote:
> But I do not want to get post from lyx-cvs!
>
> Günter
IIRC you can configure the list to not receive any email, as it is usual for
other lists.
Regards,
--
José Abílio
On 2015-07-11, Richard Heck wrote:
> On 07/11/2015 01:02 PM, Jean-Marc Lasgouttes wrote:
>> Maybe subscribe to thé list with his @lyx.org address ?
> Yes, subscribe to lyx-cvs in particular. Only subscribers can post there.
But I do not want to get post from lyx-cvs!
Günter
On 07/11/2015 01:02 PM, Jean-Marc Lasgouttes wrote:
Maybe subscribe to thé list with his @lyx.org address ?
Yes, subscribe to lyx-cvs in particular. Only subscribers can post there.
rh
Maybe subscribe to thé list with his @lyx.org address ?
JMarc
Le 11 juillet 2015 18:52:56 GMT+02:00, Scott Kostyshak a
écrit :
>He has been using his @lyx.org account. Does anything else need to be
>done?
>
>Scott
He has been using his @lyx.org account. Does anything else need to be done?
Scott
On Thu, Mar 13, 2014 at 10:27 AM, Benjamin Piwowarski wrote:
>
> On Thu, Mar 13, 2014 at 10:25 AM, Vincent van Ravesteijn
> wrote:
>>
>> Hi Benjamin,
>>
>> Can you subscribe yourself with the lyx.org e-mail address to
>> lyx-...@lists.lyx.org ? Otherwise, your commit are not sent to this
>> list
Hi Benjamin,
Can you subscribe yourself with the lyx.org e-mail address to
lyx-...@lists.lyx.org ? Otherwise, your commit are not sent to this
list.
Vincent
Scott Kostyshak wrote:
> On Sat, Dec 29, 2012 at 11:34 AM, Richard Heck wrote:
>> On 12/29/2012 11:15 AM, Scott Kostyshak wrote:
>>>
>>> On Sat, Dec 29, 2012 at 10:48 AM, Richard Heck wrote:
This can be done. It's a matter of updating the script that sends these
emails. I'll try t
y try to keep up-to-date on pushes to the repo by reading
>>>> the lyx-cvs emails. However, I just realized that I might be missing
>>>> some commits that I would be interested in because when someone pushes
>>>> more than one commit at once, it is stacked in one
On 12/29/2012 11:15 AM, Scott Kostyshak wrote:
On Sat, Dec 29, 2012 at 10:48 AM, Richard Heck wrote:
On 12/28/2012 09:32 PM, Scott Kostyshak wrote:
I currently try to keep up-to-date on pushes to the repo by reading
the lyx-cvs emails. However, I just realized that I might be missing
some
On Sat, Dec 29, 2012 at 10:48 AM, Richard Heck wrote:
> On 12/28/2012 09:32 PM, Scott Kostyshak wrote:
>>
>> I currently try to keep up-to-date on pushes to the repo by reading
>> the lyx-cvs emails. However, I just realized that I might be missing
>> some commits th
On 12/28/2012 09:32 PM, Scott Kostyshak wrote:
I currently try to keep up-to-date on pushes to the repo by reading
the lyx-cvs emails. However, I just realized that I might be missing
some commits that I would be interested in because when someone pushes
more than one commit at once, it is
I currently try to keep up-to-date on pushes to the repo by reading
the lyx-cvs emails. However, I just realized that I might be missing
some commits that I would be interested in because when someone pushes
more than one commit at once, it is stacked in one email. The top one
might be "typos
>
>
> Vincent, if it is so important for you to not get big emails, then you
> really have to solve that at your side. Sorting into folders, forwarding
> only small mails, only getting headers etc. You cannot really expect
> people/mailes/svnmailer what ever to solve that for you.
>
No, but one ha
Le 27/05/2011 10:52, Lars Gullik Bjønnes a écrit :
But I can agree that the mails from mailer.py is a bit on the large side
at some times.
Yes, we need something better than mailer.py, but it does not seem
trivial enough to me.
JMarc
Vincent van Ravesteijn writes:
| On Mon, Mar 28, 2011 at 11:25 PM, Jean-Marc Lasgouttes
| wrote:
>
>> Le 28/03/11 19:31, Tommaso Cucinotta a écrit :
>>
>> I can see this was not implemented (see last 2.8MB commit r38082).
>>>
>>> I know there are more important things to think about, however, jus
On Mon, Mar 28, 2011 at 11:25 PM, Jean-Marc Lasgouttes
wrote:
> Le 28/03/11 19:31, Tommaso Cucinotta a écrit :
>
> I can see this was not implemented (see last 2.8MB commit r38082).
>>
>> I know there are more important things to think about, however, just to
>> not
>> forget about this . . . .
>>
Le 17/04/11 23:39, Pavel Sanda a écrit :
This is done now. (easier than pmwiki!)
good news, thanks
For pmwiki I am not even able to understand how the current booki3Ai
password is set. Grep does not turn it up, either in plain text, not in
crypt()ed version. I am not sure what Christian did
Jean-Marc Lasgouttes wrote:
> Le 02/04/11 16:32, Pavel Sanda a écrit :
>> btw could we get updated doxygen documentation on the server?
>> pavel
>
> This is done now. (easier than pmwiki!)
good news, thanks
pavel
Le 02/04/11 16:32, Pavel Sanda a écrit :
btw could we get updated doxygen documentation on the server?
pavel
This is done now. (easier than pmwiki!)
JMarc
Jean-Marc Lasgouttes wrote:
> "apt-get install svnmailer" is rather intimidating. Why would I let it
> install subversion??
my advice was for the case svnmailer is already there and configured.
i wouldn't risk to break svn server by udpating ;)
btw could we get updated doxygen documentation on t
Le 28/03/11 23:30, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Le 28/03/11 19:31, Tommaso Cucinotta a écrit :
I can see this was not implemented (see last 2.8MB commit r38082).
I know there are more important things to think about, however, just to
not
forget about this . . . .
I actua
Jean-Marc Lasgouttes wrote:
> Le 28/03/11 19:31, Tommaso Cucinotta a écrit :
>> I can see this was not implemented (see last 2.8MB commit r38082).
>>
>> I know there are more important things to think about, however, just to
>> not
>> forget about this . . . .
>
> I actually looked at it a few day
Le 28/03/11 19:31, Tommaso Cucinotta a écrit :
I can see this was not implemented (see last 2.8MB commit r38082).
I know there are more important things to think about, however, just to not
forget about this . . . .
I actually looked at it a few days ago. It turns out that our mails are
creat
Il 17/02/2011 01:26, Pavel Sanda ha scritto:
Tommaso Cucinotta wrote:
If it is not too difficult, I would propose to cut the attached patches to
a maximum size,
+1
JMarc, this should be just one option in the svn hook scripts.
I can see this was not implemented (see last 2.8MB commit r38082)
Il 17/02/2011 01:22, Tommaso Cucinotta ha scritto:
I'd like to know whether anyone else (apart from myself) has some
troubles with those so long refactoring/new-features patches entirely
sent to the lyx-cvs e-mail box.
just to support the argument: the dictionary e-mail of yesterday
Tommaso Cucinotta wrote:
> If it is not too difficult, I would propose to cut the attached patches to
> a maximum size,
+1
JMarc, this should be just one option in the svn hook scripts.
pavel
Hi all,
I'd like to know whether anyone else (apart from myself) has some
troubles with those so long refactoring/new-features patches entirely
sent to the lyx-cvs e-mail box.
I'm sure I'm using a so bad e-mail client like Thunderbird, however when
opening one of those e-ma
Christian Ridderström wrote:
> Is the size a problem?
for me no.
> If so, what can I do to avoid it?
in svnmailer.conf i see for_repos and for_paths variables.
pavel
Hi,
When comitting changes to web pages, the attached 'patches' are
unfortunately rather big. I see that the automatically generated posts are
in the order of 40k to 80k sometimes.
Is the size a problem?
If so, what can I do to avoid it?
/Christian
--
Christian Ridderström, +46-8-768 39 44
Oh, I certainly meant that the text should be reduced to a SHA-1.
I agree it does not make sense to only reduce the insets.
Regards,
Asger
Alfredo Braunstein wrote:
> Asger Ottar Alstrup wrote:
>
>> Alfredo Braunstein wrote:
>>> Amazing review, thanks. On a fast read, I've found that the variant that
>>> perfectly fits our edition/CT capabilities is 1-degree, unit cost edit
>>> distance. Unfortunately the algorithm cited for this pu
Asger Ottar Alstrup wrote:
> Alfredo Braunstein wrote:
>> Amazing review, thanks. On a fast read, I've found that the variant that
>> perfectly fits our edition/CT capabilities is 1-degree, unit cost edit
>> distance. Unfortunately the algorithm cited for this purpose [Sel77,
>> Didn't look at it
Alfredo Braunstein wrote:
Amazing review, thanks. On a fast read, I've found that the variant that
perfectly fits our edition/CT capabilities is 1-degree, unit cost edit
distance. Unfortunately the algorithm cited for this purpose [Sel77, Didn't
look at it yet, though.] seems to have time and spa
Alfredo Braunstein wrote:
> (and by the way, this seems roughly
> similar to what you get with string edit distance in which insets are
> symbols of an extended alphabet with cost of substitution recursively
> defined as edit distance, using plain Levenshtein algorithm)
...and this is esentially
Asger Ottar Alstrup wrote:
> See
>
> http://arxiv.org/abs/0708.4288
>
> for a recent ph.d. dissertation that contains a bunch of improved
> algorithms for doing tree diffs, and much more.
Amazing review, thanks. On a fast read, I've found that the variant that
perfectly fits our edition/CT capa
Alfredo Braunstein wrote:
[*] There are many of them. Actually it is not really straightforward
because the data structure in LyX is not linear but rather a tree, but I
think this issue can be solved. Another possible problem is that best known
algorithm are worst case O(N^2) where N is the size
On Mon, 03 Sep 2007 14:45:58 +0100
José Matos <[EMAIL PROTECTED]> wrote:
> On Monday 03 September 2007 13:01:21 Tommaso Cucinotta wrote:
> >
> > Now, think at all of this in a future in which LyX might embrace
> > XML-based representation of documents (I've read smth. like
> > that on the list). T
On Monday 03 September 2007 13:01:21 Tommaso Cucinotta wrote:
>
> Now, think at all of this in a future in which LyX might embrace
> XML-based representation of documents (I've read smth. like
> that on the list). The simple text-based
> diffing tools would produce an output that is harder and hard
On Mon, 2007-09-03 at 12:34 +0100, José Matos wrote:
> On Monday 03 September 2007 12:25:53 Darren Freeman wrote:
> > But I can't see it happening anytime soon or ever..
>
> Just curious, why?
Wouldn't it be a huge amount of work?
Okay I retract that. I can't see it happening soon :)
It would
Darren Freeman ha scritto:
If you haven't used it, give "kompare" a go. For regular text files,
it's fantastic!
Actually, my preferred CVS manager is the one within Eclipse
(even for articles) :-)
Although this isn't the nicest solution, it gets you partway there. If
you can read raw LyX you
Tommaso Cucinotta wrote:
> Hi,
>
> I'd like to know if there is any planned support to CVS/SVN
> diff of .lyx files. Something that shows a double-work area
> window with my local version on the left and the remote
> committed version on the right, highlighting in both work-areas
> the changes be
On Monday 03 September 2007 12:25:53 Darren Freeman wrote:
> But I can't see it happening anytime soon or ever..
Just curious, why?
> Have fun,
> Darren
--
José Abílio
On Mon, 2007-09-03 at 12:12 +0200, Tommaso Cucinotta wrote:
> diff of .lyx files. Something that shows a double-work area
> window with my local version on the left and the remote
> committed version on the right, highlighting in both work-areas
> the changes between the two (this might be done [ g
Hi,
I'd like to know if there is any planned support to CVS/SVN
diff of .lyx files. Something that shows a double-work area
window with my local version on the left and the remote
committed version on the right, highlighting in both work-areas
the changes between the two (this might be done [ gra
> "OpenMacNews" == OpenMacNews <[EMAIL PROTECTED]> writes:
OpenMacNews> but, subsequent 'make' eventually (!) dies at:
[...]
OpenMacNews> with the rather UNHELPFUL message:
OpenMacNews>cannot find the library `'
Try to look at the .la files that are referenced on the command line
(these
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Lars Gullik Bjønnes wrote:
> OpenMacNews <[EMAIL PROTECTED]> writes:
>
> | hi all,
> |
> | bldg lyx cvs head (13 Feb 06) on OSX 10.4.4, config'd as:
> |
> | ./autogen.sh
> |
> | setenv LDFLAG
OpenMacNews <[EMAIL PROTECTED]> writes:
| hi all,
|
| bldg lyx cvs head (13 Feb 06) on OSX 10.4.4, config'd as:
|
| ./autogen.sh
|
| setenv LDFLAGS "-framework Carbon -framework OpenGL -framework AGL
-framework QuickTime -lz"
Why the '-lz'? I wo
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi all,
bldg lyx cvs head (13 Feb 06) on OSX 10.4.4, config'd as:
./autogen.sh
setenv LDFLAGS "-framework Carbon -framework OpenGL -framework AGL
-framework QuickTime -lz"
./configure \
--prefix
On Sun, Oct 16, 2005 at 06:46:40PM +0200, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | Is it normal to get mails like
>
> Only when I just recently discoverd that the mailinglist was stuck and
> just collected emails, but sent none out...
Ah, well.
So maybe next
Andre Poenitz <[EMAIL PROTECTED]> writes:
| Is it normal to get mails like
Only when I just recently discoverd that the mailinglist was stuck and
just collected emails, but sent none out...
--
Lgb
Is it normal to get mails like
Delivered-To: [EMAIL PROTECTED]
Received: from localhost (localhost [127.0.0.1])
by millo.mpi.htwm.de (Postfix) with ESMTP id C0F7B80151
for <[EMAIL PROTECTED]>; Fri, 14 Oct 2005 19:31:49 +0200 (CEST)
Envelope-
On Sat, Sep 24, 2005 at 09:11:19AM +0300, Martin Vermeer wrote:
> I propose to put the attached summarizing patch in, and test and
> profile again.
At least the update parts could be committed immediately as far as I am
coconcerned. They fix regressions.
Andre'
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> OK ... I've tried this, and it looks like
Bennett> --disable-assertions creates problems requiring that
Bennett> #include
Bennett> be added to each of the following:
Bennett> src/factory.C src/messages.C src/text.C src/text2.
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
Lars> Or almost... leave assertions in f.ex.
Jean-Marc> So, would the following patch be OK?
Applied.
JMarc
On Sat, 24 Sep 2005 10:34:25 +0100 Angus Leeming <[EMAIL PROTECTED]> wrote:
> Martin Vermeer wrote:
> > I propose to put the attached summarizing patch in, and test and
> profile
> > again.
>
> My comments are those of someone who is entirely ignorant of this part
> of
> the code, so please take
Martin Vermeer wrote:
> I propose to put the attached summarizing patch in, and test and profile
> again.
My comments are those of someone who is entirely ignorant of this part of
the code, so please take them with a pinch of salt. Well meaning
interference :)
Angus
Why the two if statements ra
On Sat, Sep 24, 2005 at 08:56:58AM +0300, Martin Vermeer wrote:
> BTW am I right in understanding that descending into the cursor stack means
> moving from bottom downward to top (tip?), increasing depth all the time? How
> logical...
Depends on your point of view. Implementation-wise it's certain
On Thu, Sep 22, 2005 at 09:06:46AM +0200, Lars Gullik Bjønnes wrote:
> | Incidentally, why don't we leave assertions in always? I'd imagine
> | that guaranteed clean up and dumping of foo.lyx.emergency was of huge
> | importance to our users.
>
> They do quite a lot to the speed...
I'd favour cor
1 - 100 of 339 matches
Mail list logo
