On Tue, Jul 04, 2000 at 11:25:15PM +0200, Lars Gullik Bjønnes wrote:
> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>
> | Tell me if it works now.
> | (wait some 22 minutes before testing...)
>
> Try now.
>
> One reason why this was not found earlier is that you are one of the
> _very_ few t
On Tue, Jul 04, 2000 at 11:13:02PM +0200, Lars Gullik Bjønnes wrote:
> Hmmm da hmm.. no we are not and I think I know what is going on...
> I guess there are some rsync magic that is wrong... let me have a
> look...
>
> Ok, a missing --delete as arg to rsync
>
> It is good that you don't give up
John Weiss wrote:
> On Tue, Jul 04, 2000 at 10:28:34AM +0200, Jean-Marc Lasgouttes wrote:
> > It happens when you cite several documents in one cite inset, as in
> > JWeiss97,JWeiss98,JWeiss98a,JWeiss99,JWeiss2000.
>
> This *is* an unfortunate problem. I don't recall if LaTeX itself
> handles su
On Tue, Jul 04, 2000 at 10:28:34AM +0200, Jean-Marc Lasgouttes wrote:
>
> It happens when you cite several documents in one cite inset, as in
> JWeiss97,JWeiss98,JWeiss98a,JWeiss99,JWeiss2000.
This *is* an unfortunate problem. I don't recall if LaTeX itself
handles such long citations. (I su
Hi!
I want to report a bug in Relyx. Try to load the file than I'm sending to
you (using the foiltex class). It was generated by lyx ,and after that
edited by hand. As you can see, when you import it to lyx, the abstract
is missing.
It seems that the \foilhead command confuses relyx.
I'm usin
I think we should do with the new features that we have put in now.
Fix them and release 1.1.6.
Stuff we need to verify:
- the new insetcite
- the dialogs moved to gui-indep
- external inset + templates
- set-color
- -geometry
- docbook/linuxdoc f
edscott <[EMAIL PROTECTED]> writes:
| Associated input tex files are created in the tmp directory,
This is only true when you include .lyx files, it is also possible to
include .tex files and they are not copied to the tmp dir.
Lgb
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Tell me if it works now.
| (wait some 22 minutes before testing...)
Try now.
One reason why this was not found earlier is that you are one of the
_very_ few that use "make dist" with a copy checket out from anoncvs.
A simple "make" should not s
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| On Tue, Jul 04, 2000 at 09:53:28PM +0200, Lars Gullik Bjønnes wrote:
| > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| >
| >
| > | as said, they are not present there.
| >
| > [larsbj@lett src]$ cvs status cite.C
| >
On Tue, Jul 04, 2000 at 09:53:28PM +0200, Lars Gullik Bjønnes wrote:
> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>
>
> | as said, they are not present there.
>
> [larsbj@lett src]$ cvs status cite.C
> ===
> File: no file cite
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| as said, they are not present there.
[larsbj@lett src]$ cvs status cite.C
===
File: no file cite.CStatus: Up-to-date
Working revision:No entry for cite.C
Rep
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| Hi folks,
|
| The latest CVS update still has the debug-compile link problem I've been
| reporting. Setting CFLAGS and CXXFLAGS to -g does not work, setting them to
| ``-g -O'' works.
messages please.
| One minor nit about the CVS repository, th
Dekel Tsur <[EMAIL PROTECTED]> writes:
| The following patch improves the multi-lingual support:
|
| 1. Add support for displaying languages with multiple charsets.
| See a screenshot at http://www.math.tau.ac.il/~dekel/lyx/unicode.png
Impressive.
| To use it, select "iso10646-1" as screen fon
Hi folks,
The latest CVS update still has the debug-compile link problem I've been
reporting. Setting CFLAGS and CXXFLAGS to -g does not work, setting them to
``-g -O'' works.
One minor nit about the CVS repository, the src/cite.C and src/cite.h are
*still* there and they produce problems for di
On 04-Jul-2000 Angus Leeming wrote:
> My head is spinning a little from all these answers, but I'd like to thank all
> of you for the ideas.
>
#:O)
[snip it as all have already read it]
>
> This way, the functionality is kept in the kernel. No new variables need to be
> stored in the inset.
My head is spinning a little from all these answers, but I'd like to thank all
of you for the ideas.
I think I'll summarise what I'm going to try and implement:
The signal in BufferView::Pimpl::workAreaButtonRelease() remains unchanged:
switch( inset_hit->LyxCode() ) {
case Inse
On 04-Jul-2000 Lars Gullik Bjønnes wrote:
> Juergen Vigna <[EMAIL PROTECTED]> writes:
>
>| Well what about:
>|
>| owner->GetDialogs()->showCitation(argument)
>|
>| but IMO this should be:
>|
>| owner->GetDialogs()->createCitation(argument)
>
> But still the dialog code should not b
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Insert Url -> press cancel should not insert anything into doc.
Lars> Insert Url -> press ok, without any more info should imho be
Lars> inserted into doc
Except that Insert URL only has a close button (that's a bug, of course
Juergen Vigna <[EMAIL PROTECTED]> writes:
| Well what about:
|
| owner->GetDialogs()->showCitation(argument)
|
| but IMO this should be:
|
| owner->GetDialogs()->createCitation(argument)
But still the dialog code should not be allowed to insert anything
into the docment. this is the
Angus Leeming <[EMAIL PROTECTED]> writes:
| But in LyXFunc I've just allocated some new memory:
| case LFUN_INSERT_CITATION:
| owner->getDialogs()->showCitation( new
| InsetCitation(argument) );
yes _are_ allowed to rewrite...
case LFUN_INSERT_CITATION: {
On 04-Jul-2000 Lars Gullik Bjønnes wrote:
> Juergen Vigna <[EMAIL PROTECTED]> writes:
>
>| On 04-Jul-2000 Lars Gullik Bjønnes wrote:
>| >
>| > We don't want owner or owner_par in LyXInsets.
>| >
>|
>| Well we already have an owner() :) and that is if the owner is another
>| inset!
>
> yes, i
On 04-Jul-2000 Angus Leeming wrote:
>
> The alternative I thought of would be:
> case LFUN_INSERT_CITATION:
> owner->getDialogs()->showCitation(0);
>
> and to control the creation of a new InsetCitation from the FormCitation class.
> This would removed the need for the Inset
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 04-Jul-2000 Lars Gullik Bjønnes wrote:
| >
| > We don't want owner or owner_par in LyXInsets.
| >
|
| Well we already have an owner() :) and that is if the owner is another
| inset!
yes, i know, but i am not sure if we really need it.
Lg
On 04-Jul-2000 Lars Gullik Bjønnes wrote:
>
> We don't want owner or owner_par in LyXInsets.
>
Well we already have an owner() :) and that is if the owner is another
inset!
I also agree that we don't need the paragraph_owner.
Jürgen
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-.
On 04-Jul-2000 Lars Gullik Bjønnes wrote:
>| I'm thinking of adding a new variable to class Inset:
>|
>| class Inset {
>| bool isInserted() const { return inserted_; }
>| bool inserted_;
>| }
>
> I don't like it, and do not see why this is needed.
>
I agree you should do as I do wit
Lars> | interrogation of inset->isInserted() will allow the dialog to decide what to do
Lars> | with the inset in the callback functions called when the Ok or Cancel buttons
Lars> | are pressed.
Lars> Should be possible to decide even without that flag.
Lars> - on cancel just do nothing
Lars> -
Lior Silberman <[EMAIL PROTECTED]> writes:
| Perhaps holding a pointer to the owning paragraph whould server us
| better?
No, I don't think so...
| Insets can be either in the top-level document (owned by a paragraph) or
| inside other insets. Thus insets have an Inset* 'owner' member, but no
On Tue, 4 Jul 2000, Angus Leeming wrote:
> I'm thinking of adding a new variable to class Inset:
>
> class Inset {
> bool isInserted() const { return inserted_; }
> bool inserted_;
> }
>
> The strategy I outline below is for an InsetCitation, but I think that it also
> holds true fo
Angus Leeming <[EMAIL PROTECTED]> writes:
| I'm thinking of adding a new variable to class Inset:
|
| class Inset {
| bool isInserted() const { return inserted_; }
| bool inserted_;
| }
I don't like it, and do not see why this is needed.
| The strategy I outline below is for an I
I'm thinking of adding a new variable to class Inset:
class Inset {
bool isInserted() const { return inserted_; }
bool inserted_;
}
The strategy I outline below is for an InsetCitation, but I think that it also
holds true for other insets and so the variable should go in the top
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 04-Jul-2000 Lars Gullik Bjønnes wrote:
| >
| > hmm I think this change a lot of my code too... but not much.
| >
|
| Well if you worked on the insetcollapsable.[Ch] YES otherwise probably
| no.
I have done some there, because we now have some 6-8
On 04-Jul-2000 Lars Gullik Bjønnes wrote:
>
> hmm I think this change a lot of my code too... but not much.
>
Well if you worked on the insetcollapsable.[Ch] YES otherwise probably
no.
>| I'll commit what I have now so you can have a look!
>
> Please, do.
>
Really soon just let me finish s
Juergen Vigna <[EMAIL PROTECTED]> writes:
| Well guys,
|
| you would mean I'm bussy with other things and therefore not comitting
| anything new, but the case is that I'm still struggling with the update
| problems and I'm still not able to solve them (I already rewrote the
| collapsable inset t
Baruch Even <[EMAIL PROTECTED]> writes:
| Anyway since it's not my call in the project I only raise the subject and
| provide the patch so that in a future time someone else will need less
| time to figure what the idea of the code is.
Variable names with more than three characters should not be
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> It is not a complicated thing. I'm sure you will be able to
Asger> figure out how to do it in half an hour.
You mean that you want _me_ to do it? Ha!
Asger> I'm not fanatic, and I don't think this problem is such a big
Angus> My question is simple: is the use of argument relevant here, or
Angus> has this piece of code been superceeded by the new insets? If
Angus> it is relevant, can someone please explain where and when it
Angus> would be used? I've removed it to see if I can find any effect:
Angus> NONE! Of cou
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> My question is simple: is the use of argument relevant here, or
Angus> has this piece of code been superceeded by the new insets? If
Angus> it is relevant, can someone please explain where and when it
Angus> would be used? I've rem
> "John" == John Weiss <[EMAIL PROTECTED]> writes:
John> Citations are not at all similar to footnotes. When writing
John> articles for technical journals, or when writing a doctoral
John> thesis, you need to see what you're referring back to, or you'll
John> get hopelessly lost!
Agreed.
Jo
Well guys,
you would mean I'm bussy with other things and therefore not comitting
anything new, but the case is that I'm still struggling with the update
problems and I'm still not able to solve them (I already rewrote the
collapsable inset to use a TextInset instead to BE a TextInset and so
I fi
39 matches
Mail list logo
