On 07-Jul-2000 Baruch Even wrote:
On Fri, 7 Jul 2000, Juergen Vigna wrote:
Is there any reason why to do that instead of just a simple:
\begin_inset Graphics
filename /tmp/platypus.png
rotate 0
display monochrome
...
\end_inset
Seems good for me!
This way seems to me to be easier
On 07-Jul-2000 Baruch Even wrote:
After some more work on the inset I've got even more questions.
1. Marking the buffer dirty. After my inset gets changed by the dialog,
how should I go about notifying lyx that the data has changed? I know of
the markxxxDirty, but how do I get access to
"Kayvan" == Kayvan Sylvan [EMAIL PROTECTED] writes:
Kayvan Content-Type: text/plain; charset=us-ascii Hi everyone,
Kayvan Te latest configure.in patch breaks configure/compilation on
Kayvan my Solaris box:
Kayvan The problem is probably related to the fact that I use the
Kayvan extra include
Reading an old lyx file with current CVS, I notice that protected blanks are
converted to
SpecialChar \-
rather than
SpecialChar ~
Angus
Pablo De Napoli [EMAIL PROTECTED] writes:
| Hi!
|
| I could not lyx-1.1.5pre3 from the sources. Something is wrong with the
| regex stuff. I'm using linux (debian distribution)
|
| g++ 2.95.2-13
| libc 2.1.2-11
| libstdc++2.10 2.95.2-13
|
| I think the problem could be caused by the changes
On 10-Jul-2000 Angus Leeming wrote:
I reported this DEC cxx warning a few days ago. It seems that the consensus was
that Inset::deleteLyXText should be a const function, but the code hasn't been
updated. If it makes life easier, here is the patch. Could someone
apply it, please.
Thanks I
At long last I think I'm back. I unsubscribed last christmas, and
never got around to subscribing again (but I've still been advocating
and defending wherever it came up :)
I'm now on the Penn State Dubois faculty, and getting my machine running.
Hopefully I can draft a student or two to turn
JMarc Angus Reading an old lyx file with current CVS, I notice that
JMarc Angus protected blanks are converted to SpecialChar \- rather than
JMarc Angus SpecialChar ~
JMarc I do not see that with a file created with LyX 1.0.3 (read correctly
JMarc with both cvs and 1.1.5fix). Do you have an
Angus Leeming wrote:
JMarc Angus Reading an old lyx file with current CVS, I notice that
JMarc Angus protected blanks are converted to SpecialChar \- rather than
JMarc Angus SpecialChar ~
JMarc I do not see that with a file created with LyX 1.0.3 (read correctly
JMarc with both cvs and
I've tried to add some elementary support of GTK/Gnome frontend to LyX.
The composed code and collection of configure .m4 scripts brings the GTK
frontend to the same level as KDE one --- showing the copyright dialog
box. In the code I used GTK-- and GNOME-- libraries (C++ wrappers of GTK
and
Marko Vendelin [EMAIL PROTECTED] writes:
| 2. Make LyX compatible with the string class included in libstdc++ by
|fixing files src/support/lstrings.C (lines 184 and 201,
|string::compare) and src/lyx_cb.C (line 1109, algorithm copy and string
|interaction).
You mean unfixing I
(I still have some difficulty sending mails.)
"Asger K. Alstrup Nielsen" [EMAIL PROTECTED] wrote:
Could you factor out this part of the patch?
Then we can look at it, and if it looks good, apply it to cvs.
I will try. But please wait!
So the font selection is based on the global LC_CTYPE?
I've patched fdfix.sh and associated makefile to allow me to make forward
declarations such as
struct FD_form_citation;
class FormCitation : public DialogBase {
FD_form_citation * dialog_;
}
rather than have to include the header file. (If I so wish. Both options are now
available.)
Hi folks,
Here is Bernard Michael Hurley's literate patch against the latest CVS.
This includes my lib/build-listerror script, re-written to work on
a generic /bin/sh, instead of requiring bash.
Please apply to CVS.
---Kayvan
--
Kayvan A. Sylvan |
On Tue, 11 Jul 2000, Juergen Vigna wrote:
1. Marking the buffer dirty. After my inset gets changed by the dialog,
how should I go about notifying lyx that the data has changed? I know of
the markxxxDirty, but how do I get access to them? basically it amounts to
"how do I get a pointer to
On 11 Jul 2000, Lars Gullik Bjønnes wrote:
Marko Vendelin [EMAIL PROTECTED] writes:
| 4. Find better implementation of STL for Linux and use its string
|class with LyX and GTK--/Gnome-- (current CVS version of gcc/libstdc++
|is not good enough to compile LyX).
the libstdc++ is
Dekel Tsur [EMAIL PROTECTED] wrote:
We need to change the internal text storage from 8-bit to 16/32-bit,
before we can use such a patch.
Yes, I realize this (and called it 2. in the previous message.)
We also want to be able to render simultaneously Japanese, Hebrew, Russia
etc. Is it
Hello, Marko!
Another solution:
1. Take the GTK--/GNOME-- headers, and use macro
to change "string" to basic_stringchar for them:
#define string basic_stringchar
#include GTK.h
#undef string
You can also create wrappers for all headers that you use
to add this macro automatically.
2. Add
Marko Vendelin [EMAIL PROTECTED] writes:
| 4. Find better implementation of STL for Linux and use its string
|class with LyX and GTK--/Gnome-- (current CVS version of gcc/libstdc++
|is not good enough to compile LyX).
Could anybody please explain once more in simple words what
On 07-Jul-2000 Baruch Even wrote:
> On Fri, 7 Jul 2000, Juergen Vigna wrote:
>
> Is there any reason why to do that instead of just a simple:
> \begin_inset Graphics
> filename /tmp/platypus.png
> rotate 0
> display monochrome
> ...
> \end_inset
>
Seems good for me!
> This way seems to me to
On 07-Jul-2000 Baruch Even wrote:
> After some more work on the inset I've got even more questions.
>
> 1. Marking the buffer dirty. After my inset gets changed by the dialog,
> how should I go about notifying lyx that the data has changed? I know of
> the markxxxDirty, but how do I get access
> "Kayvan" == Kayvan Sylvan <[EMAIL PROTECTED]> writes:
Kayvan> Content-Type: text/plain; charset=us-ascii Hi everyone,
Kayvan> Te latest configure.in patch breaks configure/compilation on
Kayvan> my Solaris box:
Kayvan> The problem is probably related to the fact that I use the
Kayvan>
Reading an old lyx file with current CVS, I notice that protected blanks are
converted to
SpecialChar \-
rather than
SpecialChar ~
Angus
Pablo De Napoli <[EMAIL PROTECTED]> writes:
| Hi!
|
| I could not lyx-1.1.5pre3 from the sources. Something is wrong with the
| regex stuff. I'm using linux (debian distribution)
|
| g++ 2.95.2-13
| libc 2.1.2-11
| libstdc++2.10 2.95.2-13
|
| I think the problem could be caused by the
On 10-Jul-2000 Angus Leeming wrote:
> I reported this DEC cxx warning a few days ago. It seems that the consensus was
> that Inset::deleteLyXText should be a const function, but the code hasn't been
> updated. If it makes life easier, here is the patch. Could someone
> apply it, please.
>
At long last I think I'm back. I unsubscribed last christmas, and
never got around to subscribing again (but I've still been advocating
and defending wherever it came up :)
I'm now on the Penn State Dubois faculty, and getting my machine running.
Hopefully I can draft a student or two to turn
JMarc> Angus> Reading an old lyx file with current CVS, I notice that
JMarc> Angus> protected blanks are converted to SpecialChar \- rather than
JMarc> Angus> SpecialChar ~
JMarc> I do not see that with a file created with LyX 1.0.3 (read correctly
JMarc> with both cvs and 1.1.5fix). Do you have
Angus Leeming wrote:
>
> JMarc> Angus> Reading an old lyx file with current CVS, I notice that
> JMarc> Angus> protected blanks are converted to SpecialChar \- rather than
> JMarc> Angus> SpecialChar ~
>
> JMarc> I do not see that with a file created with LyX 1.0.3 (read correctly
> JMarc> with
I've tried to add some elementary support of GTK/Gnome frontend to LyX.
The composed code and collection of configure .m4 scripts brings the GTK
frontend to the same level as KDE one --- showing the copyright dialog
box. In the code I used GTK-- and GNOME-- libraries (C++ wrappers of GTK
and
Marko Vendelin <[EMAIL PROTECTED]> writes:
| 2. Make LyX compatible with the string class included in libstdc++ by
|fixing files src/support/lstrings.C (lines 184 and 201,
|string::compare) and src/lyx_cb.C (line 1109, algorithm copy and string
|interaction).
You mean unfixing I
(I still have some difficulty sending mails.)
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> wrote:
> Could you factor out this part of the patch?
> Then we can look at it, and if it looks good, apply it to cvs.
I will try. But please wait!
> So the font selection is based on the global
I've patched fdfix.sh and associated makefile to allow me to make forward
declarations such as
struct FD_form_citation;
class FormCitation : public DialogBase {
FD_form_citation * dialog_;
}
rather than have to include the header file. (If I so wish. Both options are now
available.)
Hi folks,
Here is Bernard Michael Hurley's literate patch against the latest CVS.
This includes my lib/build-listerror script, re-written to work on
a generic /bin/sh, instead of requiring bash.
Please apply to CVS.
---Kayvan
--
Kayvan A. Sylvan |
On Tue, 11 Jul 2000, Juergen Vigna wrote:
> > 1. Marking the buffer dirty. After my inset gets changed by the dialog,
> > how should I go about notifying lyx that the data has changed? I know of
> > the markxxxDirty, but how do I get access to them? basically it amounts to
> > "how do I get a
On 11 Jul 2000, Lars Gullik Bjønnes wrote:
> Marko Vendelin <[EMAIL PROTECTED]> writes:
>
> | 4. Find better implementation of STL for Linux and use its string
> |class with LyX and GTK--/Gnome-- (current CVS version of gcc/libstdc++
> |is not good enough to compile LyX).
>
> the
Dekel Tsur <[EMAIL PROTECTED]> wrote:
> We need to change the internal text storage from 8-bit to 16/32-bit,
> before we can use such a patch.
Yes, I realize this (and called it 2. in the previous message.)
> We also want to be able to render simultaneously Japanese, Hebrew, Russia
> etc. Is
Hello, Marko!
Another solution:
1. Take the GTK--/GNOME-- headers, and use macro
to change "string" to basic_string for them:
#define string basic_string
#include
#undef string
You can also create wrappers for all headers that you use
to add this macro automatically.
2. Add operator
> > Marko Vendelin <[EMAIL PROTECTED]> writes:
> >
> > | 4. Find better implementation of STL for Linux and use its string
> > |class with LyX and GTK--/Gnome-- (current CVS version of gcc/libstdc++
> > |is not good enough to compile LyX).
Could anybody please explain once more in
38 matches
Mail list logo
