On Fri, 4 Feb 2000, Kevin Atkinson wrote:
> > I've already said you might be better off wrapping ispell with your aspell
> > C++ interface and then once that works worry about a C wrapper.
>
> My Aspell C++ interface using exceptions, and templates. If you can
> compile and use my interface you
The following patch fixes URL insets in Hebrew text
Index: paragraph.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/paragraph.C,v
retrieving revision 1.32
diff -u -p -r1.32 paragraph.C
--- paragraph.C 2000/02/04 09:38:30 1
When LyX is parsing the Latex log file (in LaTeX::scanLogFile),
it misses some of the errors because it assumes that the line-number of the
error appears in the next line after the "! LaTeX Error:" line,
which is not always the case.
I've attached a patch that fixes that (I'm assuming that after
I should point out that I am using version 1.1.2
On Fri, 4 Feb 2000, Walter Tautz [MFCF] wrote:
> Failed to share colors. Using private colormap
> LyX: Creating directory /u1/wtautz/.lyx/ and running configure...
> sh: configure: not found
> LyX: Done!
> LyXTextClassList::Read: unable to find
Guys
> I have just released a new stable release.
Ahhh, a new release. Always good news. Maybe time to update the web site
again?
Avagoodweekend,
Ben
Failed to share colors. Using private colormap
LyX: Creating directory /u1/wtautz/.lyx/ and running configure...
sh: configure: not found
LyX: Done!
LyXTextClassList::Read: unable to find textclass file `~/'. Exiting.
LyXSetStyle: an error occured during parsing.
Exiting.
the error
On Tue, Feb 01, 2000 at 12:36:38PM +, Jules Bean wrote:
> > If the language of the document is Hebrew:
> > Use "\locallanguage hebrew" to switch to English
> > "\locallanguage default" to return to Hebrew
>
> Surely it would be "\locallanguage english" to switch to English?
Yes.
> In
The following patch select the correct type of double quotes:
If the cursor is on Hebrew text, it uses InsetQuotes::SwedishQ quotes.
Otherwise, it uses the bufferparams settings.
Index: src/BufferView2.C
===
RCS file: /usr/local
Compiling the latest CVS version gives the following error
TextCache.C: In function static void TextCache::show(class ostream &, const class
LyXText *)':
TextCache.C:79: no match for call to (show_text) (LyXText *)'
TextCache.C:61: candidates are: show_text::operator ()(LyXText *&)
make[2]: ***
On 04-Feb-2000 Reuben Thomas wrote:
> Nice to see the new date insertion command, but the comment in
> lyxrc.example is a bit weird; how about:
>
># Default format string for the date-insert command
>#
># This accepts the normal strftime formats; see man strftime for full
># details of the forma
Nice to see the new date insertion command, but the comment in
lyxrc.example is a bit weird; how about:
# Default format string for the date-insert command
#
# This accepts the normal strftime formats; see man strftime for full
# details of the format.
#
(in any case, "nowing" should be "knowing
On Thu, Feb 03, 2000 at 01:54:11PM -0800, Kayvan A. Sylvan wrote:
> Hi everyone, the CVS source (1.1.5cvs) now has the hebrew patch.
>
> Is there any writeup of how to use it anywhere in the CVS archive?
>
> Thanks for any pointers!
>
I'm attaching short instructions. Note that the Hebrew keym
Nicolas SABOURET <[EMAIL PROTECTED]> writes:
| Hi.
| The bug I submit is surely already known, but I didn't find it on the
| list archive, so, just in case ...
|
| Using lyx 1.0.4 on a Linux Redhat6.1 with gnome, when I create a
| directory with a space in the name (ex: "my dir") and put a lyx f
Hello,
the patch should probably be (at filetools.C:909, in 1.1.4)
last_dot = oldname.rfind('.');
if (last_dot < last_slash &&
last_slash != string::npos &&
last_dot < last_slash )
last_dot = string::npos;
Should I send a true pat
On Fri, 4 Feb 2000, Allan Rae wrote:
> On Fri, 4 Feb 2000, Kevin Atkinson wrote:
>
> > On 3 Feb 2000, Lars Gullik Bjønnes wrote:
>
> > > C is not good for C++ programs. (usable yes, but not good)
> >
> > Do the other developers fell that way?
>
> I've already said you might be better off wrap
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 03-Feb-2000 Michael Meskes wrote:
| > On Thu, Feb 03, 2000 at 03:58:02PM +0100, Lars Gullik Bjønnes wrote:
| >> | + for (int i = 0; i < datetmp_len; i++) {
| >>
| >> In C++ it is adviced to use preincrement instead of postincrement:
| >
| > Co
Andre Poenitz <[EMAIL PROTECTED]> writes:
| Because sometimes it is necessary to create an extraneous copy of the
| iterator when using postincrements. This wastes resources.
|
| It's more or less the following:
|
| ++i:
|i = i + 1
|return i
|
| i++:
|temp = i
Hi.
The bug I submit is surely already known, but I didn't find it on the
list archive, so, just in case ...
Using lyx 1.0.4 on a Linux Redhat6.1 with gnome, when I create a
directory with a space in the name (ex: "my dir") and put a lyx file in
it, it produces an error during compilation :
"erro
Andre Poenitz <[EMAIL PROTECTED]> writes:
| > Silly question, what is that string::npos?
|
| This is the index of the last character in the string plus one.
| At least I think so ;-)
You thought wrong.
It is the maximum amount of chars possible amount of chars in a string
+ 1. It is often the
On 04-Feb-2000 Allan Rae wrote:
> On Fri, 4 Feb 2000, Kevin Atkinson wrote:
>
>> On 3 Feb 2000, Lars Gullik Bjønnes wrote:
>> [...]
>> > | modern C++ which means it is not the most portable thing in the
>> > | world.
>> >
>> > Perfect for LyX then.
>>
>> But you want to maintain compatibility
On 03-Feb-2000 Michael Meskes wrote:
> On Thu, Feb 03, 2000 at 03:58:02PM +0100, Lars Gullik Bjønnes wrote:
>> | + for (int i = 0; i < datetmp_len; i++) {
>>
>> In C++ it is adviced to use preincrement instead of postincrement:
>
> Could anyone please enlighten me and tell me why preincrem
21 matches
Mail list logo
