> --nextPart2143034.hU0dofkB2d
>
> Actually, once you've got your head around the fact that nobody is
> there to hold your hand, it isn't too bad. The attached trial program
> has been tested and is always safe. I'm going to commit this to
> XForms cvs.
>
Unfrotunately Angus' fix is buggy too, be
The cases environment defined by the ams package clashes with the plain TeX
\cases command due to the implementation of \begin in LaTeX. If the AMS
version was the right thing then I could live with this--unfortunately the AMS
cases environemnt is a plain in the butt to use. Instead of
$f(x)=\cas
The fact that queues do not have swap() methods, or fast reverse or merge
methods, means I usually end up implementing my own versions---sometimes I use
a special opeation so heavily it must be fast. word2x attatches one queue to
the end of another queue very frequently, for example and has it's o
g++ 3.3 complains about passing insettext.C passing a non-lvalue to max. The
following patch fixes this problem. Someone please apply.
--- src/insets/insettext.C.dist Tue Feb 4 10:21:03 2003
+++ src/insets/insettext.C Tue Feb 4 10:25:08 2003
@@ -312,7 +312,9 @@
int InsetText::width(Bu
The following patchlet fixes compiling with glibc 2.3.1 which dies because the
strerror declaration in src/config.h fails to match that in string.h (which
adds throw(); to the end and is therefore different). There is of course some
impact on the configure script not included in the patchlet. AFAI
In glibc wchar_t is 32 bits. Windows wide characters are UCS-2 or were last
time I ran into them. UTF8 is probably the right thing for storing the text in
a file IMHO but there are other choices.
But for GNU systems `wchar_t' is always 32 bits wide and,
therefore, capable of representi
> Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> | On Wed, Nov 27, 2002 at 04:16:16PM +0100, Jean-Marc Lasgouttes wrote:
> | >
> | > Probably not. I guess it is a consequence of our changing from
> | > \centering to center environments and friends.
> |
> | \begin{center} is bad as it adds space.
> |
There is a bug in the macro which tried to that but unfortunately left out the
middle argument (which probably why it did not work). If autoheader is not
noticing that then I think AH_TEMPLATE is the right thing (presumably as part
of the macro, that happens irrespective of the result).
I could g
Some electrons claimed that Jean-Marc Lasgouttes write:
>
> Ben> 2) does not define HAVE_DECL_MKSTEMP, but my system has it.
>
> Lars, the LYX_DECL_HDR is broken: it does not create a define in
> config.h. I do not know what to do about it, actually
>
> JMarc
>
Do you need some compile time sw
On Mon, Nov 04, 2002 at 07:29:26PM +0200, Dekel Tsur wrote:
> It shouldn't be much of problem. The solution is to do something similar
> to what is done when pressing ctrl+b inside \mathbf inset:
> When the user inserts any math element inside \textrm,
> lyx should exit the \textrm inset if the cur
If I understood it correctly last time I saw it epsi files are eps files with a
comment that contans a bitmap representation of the image. Un*x systems usually
have ghostscript and at least some programs that know one of the way to use it
(xdvi knowns how to get ghostscript to render into a windo
If LyX is following me and thinking that LyX should be using anonymous pipes
(multiple, at least one for input and one for ouput) or a pair of connected
sockets crreated by socketpair(2) for remote connections then it is much
simpler.
Neither pairs of pipes or pairs of connected sockets of neve
In addition to marking the default is there any good reason why a "default"
button could not hiughlight the default options too, so if * is a selected
option and o an selected one and the jsutificaion section reads
o full (default)
* left
o center
o right
then pressing the default button
Do I understand the design? I think the design is that an event invokes the
local inset's dispatch() function, which either handles it or passes it up to
it's parent inset. If this is not the design dare I suggest this is what it
should be? Things like end would work everywhere for free, presumab
Juergen Vigna wrote assert that
> No as Albert Chin explained us recently it is an xforms bug. When
> creating .a libraries they should contain all other needed libraries or
> at least contain the dependencies on them when build.
Stop right there. This would be a really *bad idea* in many inst
I get the feeling this is a library format issue: according to the libtool
documentation some library formats can cope with dependencies, for example I
can link an elf shared library with another one and it will automatcially pull
in the shared library it depends upon.
Some other format, for exa
Would it be relevent to mention that in TeX tabular and matricies *are*
implemented using the same basic command, namely \halign? Matricies construct
math boxes using a template contianing math shifts (aka $ signs) and tabular
uses a template without math shifts. Plain TeX's \cases uses a templat
>
>One more suggestion: naked pointers are evil. Naked pointers in an STL
>container are doubly evil. Wrap that pointer in a boost::shared_ptr. Memory
>is automatically delete-d as the list goes out of scope.
IMHO wasting cycles mainating reference counts when I know the lifetime of an
item an
You need to be careful with \cases and quite a few other similar items. If you
look at how \begin and \end work, \begin{foo} is equivilent to \foo and
\end{foo} to \endfoo. If you do not load the appropiate ams style file then you
get the plain TeX version of \cases (a macro based on a halign, se
> Hi,
> just to include my favorite platform, alpha. You have to change the file
> lyx-1.2.0/boost/boost/detail/limits.hpp
> on line 43 to
> #elif defined(__i386__) || defined(__alpha__)
> And yes, the alpha is little endian.
>
>
Surely a better fix would be to include endian.h, or if you are
How about
Use AMS math: (*) automatic (recommended) ( )Yes ( )No
and even perhaps
Validate LaTeX: ( ) Automatic (*)Yes (recommended) ( )No
where automatic would guess whether it could cope with the LaTeX/plain TeX and
not validate it if saw something odd. This could just be a minimal scan
Building shared libraries is different on lots of platforms. There are quite a
lot of things common to various platforms (compiling with -fPIC) and oodless of
little differences. IMHO libtool is the right thing if you might want to build
a shared library and, in my experience, libtool works well
Surely deleteing superflous spaces is just a matter of M-x
delete-trailing-whitespace, which you learn about under the Display, Trailing
whitespace. It operates in the whoole buffer so hit C-x n n (narrow to region)
if you want to restrict it to an area of a buffer, and C-x n w (widen) when you
w
Asger writes
>A buffer should contain a number of buffer wide data.
>This could be a list of bibliographic entries, or a list
>of labels. This information naturally belongs in the buffer.
Why? I fail to see the need, unless somewhere wants a list of references
refered to in the buffer. I can n
This a a *TeX question... and actually not too hard to answer
The simplest \usepckage{zed-csp.sty} and then the symbol is \interleave (as you
would expect if you know CSP). Expanding macros tells you \interleave is
equivielent to
\mathrel{\mathord{\mid}\mkern-2mu\mathord{\mid}\mkern-2mu\mathord{
Hmmm... you could always use ERT for conditionals. Plain TeX has conditionals
which shoud do what you need and there is a LaTeX package for those that want a
slightly prettier version. The LaTeX package might not support the plain TeX
magic documented in the rest of the message.
\begin{Plain TeX
gcc --version on most releases of gcc 3.1 generates spo,ething along the lines
of:
gcc (GCC) 3.1 20020118 (experimental)
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS
gcc 3.1 compiles LyX fine modulo one detail---the last link step makes ld grow
to a really vast size and _eventually_ die due to lack of memory. 64Mb of real
memory+50Mb swap is enough for gcc, glibc (2.2.5), XFree86 and everything else
IO have tired except lyx. I might try again once my box gets
More careful reading of the rename(2) man page reveals it does mention
problems crossing mount points. The ERRORS section of the link rename(2)
function includes
EXDEV oldpath and newpath are not on the same filesystem.
mv is smart enough to copy the file and delete the original if re
> On Fri, 25 Jan 2002, Jürgen Vigna wrote:
> - I don't know yet how to get a "justified" text in a cell, if it
> is possible, and if there is one reason to do that !
This this probably easiest to do with plain TeX. For just one line try \hbox to
{} and be sure to include some flexible g
If you are going the ERT route, you might want to do the adjustments in a group
instead and make the changes in a way that is limited to the group---easy if
you use plain TeX. The lengths are plain TeX too... pure LaTeX users would
proably do this with a list environment. Remember to ensure the p
> On Mon, 10 Sep 2001, Andre Poenitz wrote:
>
> But I am not fully convinced that minipages provide a proper solution for
> indenting a paragraph by, e.g., 5cm. You would have to set the width of
> the minipage to \textwidth-5cm and place a \hfill in front of the
> minipage. I wonder if this is
Breaking ligatures should be done with {}, \hbox{} or soemthing like that.
Using an italic correction, \/, will do the *wrong thing* on slanted or italic
words that are not split where you hide the ligature. In upright fonts allmost
all the italic corrections are zero so you will not notice th
I am pretty sure that either the TeXbook or Lesile Lamport's LaTeX users guide
says \not is a slash with width 0 (and rather obviously ink outside it's
official boundary). Whether that is the cleanest way to implement it in LyX is
not a question I am qualified to comment on.
--
Duncan (-:
"s
> On Wed, 30 May 2001, Allan Rae wrote:
> Actually we could perhaps provide a warning message like:
>
> Are you serious? GCC-2.96 is unofficial crap!
>
... and the current version number the mainline gcc sources claim to be is
3,1. I use 3.1 regularly and have the CVS version of gcc 2
> hmm, yes it does. Yesterday it was causing errors, but it seemed
> horribly confused in general.
>
Was this due to attemtoing constrcutions along the lines of x^2'', which
probably makes TeX complain about a double subscript (in addition to presumably
being the wrong thing, etc)? If you rea
File nmes with spaces in them seem to turn up on a semi-regular basis, so I
was wondering whether a patch that spotted them and applied catcode magic when
they did appear would be in order. If so would a pure TeX solution. which
would make hevay uise of \epandafter in addition to catcode magic
If nobody applied my previous patch, this one might be more tempting. The
math_Parser code is a mess, and does not follow TeX anyway (which has the
benefit of making the code simpler anyway). While it is buggy, for example
only letter, category 11 to be precise, should quality for multiple cha
This patch replaces a couple of 255s with (N(yytext)-1), which keeps up with
changes in the size of yytext. As a bonus it communicates with me what the
significance of the value to me. The macro recogniser could still be improved
(take 1 character and look for multiple character if the catcode
Some local electrons alleged that Albert Chin-A-Young
<[EMAIL PROTECTED]> said:
<...lots snipped...>
> Not all packages use their own vsnprintf() regardless of whether or
> not the system has one. Lftp certainly does not. And, I don't think
> Samba does either. Anyway, on HP-UX 10.20, patch PHCO_
OK, you need a float with some plain TeX inside it. I would suggest something
along the lines of \hbox to {\hfil\brule width 0pt height h
depth d} where h+d=.. The dimensions can be in any
suported units, which include cm (centimeters), in (inches) and pt (points).
Using a single rule for th
You do not know that the test compiles without warnings. The test decides
whether you have snprintf by attempting to link a small program conatining
snprintf. In particular it can succeed even if the declaration is not in the
header files the example #include's. The declarations in some of the
Some of my electrons alleged that Alejandro Aguilar Sierra typed:
> =
> I know nothing about the new mathed (which might actually works similar=
ly =
> to the way proposed below), but I wonder if it might be better to write=
an
> even newer mathed: the math inset will be a derived class of inse
Well, if you insit on using a single _ prefix you can get burned. It is knwon
and systenm lbraries make hevay use of names starying with _ to avoid names in
your programs. If you had used ObjectRec instead of _ObjectRec you would have
avodied trouble. However there is more... X11/XInstric.h, a
In general it is *very dangeruous* to assume that this or that header is not
included for any reason. The chance of this "non bug" ot breaking a {Open Mo,
Mo,Less}tif port is at least 99.99% (my estimate is 120%). Anything that needs
Xmu or Xt is probably fatal. If you are going to use X11 the
If the code quoted is typical then it could all be replaced by XlookupColorn
which returns the closest and exact colour
XLookupColor(dipslay, colour map, colorname, exact_ef_retrurn,
scrren_def_retrun)
Returns: 0 on mailure, non zero on success .Possible errors are BadName
(invalid colour)
To paraphrase from Vchapter 7 of Xlib programming (page 193) it says
Whe XAllocNamedColor, XlookupColor, XparseColor and XStoreNamedColor (or their
device indepent analogues) and pased a colour string thyey attempt the
following thins (and take the first that works)
1. Attempt to parse is as
> On Tue, Nov 28, 2000 at 10:30:34AM +0100, Rainer Dorsch wrote:
> >
> > Hi,
> >
> > I am not sure, if this is a known problem, but underscores in index entires
> > have to be quoted, e.g. CVS_ROOT. Otherwise an error is thrown at the
> > beginning of the document.
> >
> > This was quite conf
I have just discovered a great way of doing code reviews and fereting out
bugs, including well buried ones.q In fatc there are several ways, all of
which tend to go together; just a write a clear and easy to read document
explaning how to code works for those who do not know already.
This wil
> =
> ## Main tread
> For xforms we can use a filedescriptor driven message queue and bind
> a callback that knows what to do with fl_add_io_callback.
> =
> Unfortunately is xforms not threadsafe so we must be very careful to
> not use xforms functions in the thread.
> =
> For a fork/exec we
word2x is designed to be retargetable, so adding another output format is not
a major problem and neither is chaning or replacing it later. If you want to
do the same in wv it is probably a lot harder (last time there is no clean
separation between the front and back end in wv).
If some C++ m
While routine use of catcode magic counts as brain damage, all spaces take is
teeling TeX that space is a letter or other character. the scope of which can
be bracketed by a group. For example one could write
{\aftergroup\input\catcode` =12\aftergroup{File name with spaces}}
which works becau
If LyX is going to detect and do special magic to deal with file names with
natsty character like spaces in them, then the current suggestions are IMHO
the wrong thing. File names with spaces, and practically anything else, can be
made to work with catcode magic (see the TeXbook).
While it wo
gcc 2.96 from CVS and glibc 2.1.2 compilation dies with
math_defs.h:145: syntax error before `&'
math_defs.h:234: `ostream' undeclared in namespace `std'
math_defs.h:234: parse error before `,'
math_defs.h:332: `ostream' undeclared in namespace `std'
math_defs.h:332: parse error before `,'
math
I emailed one of the major devleopers, not quite sur who, a lfew days back a
proper solution based on the followiing fragment
\long\def\hw#1{{\halign{%
\hfil{\bf ##\unskip:\ }&\vtop{\parindent=0pt\hsize=\dimen0##\hfil\par}\cr%
#1\crcr}}}
\long\def\hl#1{%
\dimen0=1000pt\setbox0=\vbox{\hw{#1}}%
\
Just tried the latets version of lyx from CVS with XFree86 4.0 non my two old
SUN 16" monitor box (none of th available console modes give a working
display, so there is no way I am going to recn#onfigure soon). It has no
cracshed on me yet but IT seesm to think nil2 is an apropaite font (tor
I ssuppose it would be possible to have sme automatic portected space logic,
provided it could be overidden. I personally like references like this[1],
without spaces. (Various people what various different styles, so I think the
hwole issue is a job for a macro or two).
Some journals referen
gcc 2.96 has trouble with the test inset too. I am sure this is a bug but not
sure what the correct fix actually is, as ignoring const is not nescarily
safe. Could someone who knows the coed better determine whether a cast,
prototype twiddle or massive code change is appropiate here?
make[3]
LyX 1.1.5cvs prudces the followng message when compiled with the latest
egcs/gcc 2.96 (which will be required on linux if LyX pulls out all the modern
C++ stops).
buffer.C:830:60: warning: #warning Verify that this else clause is still
needed. (Lgb)
buffer.C: In method `void Buffer::SimpleLin
I have a macro that will test whether compilers like a given option. You might
be better to probe for compiler options at configure time, which should take
fewer updates and compiler specific knowledge.
Use is moderately simple, an example is
dps_CC_OPTION(warn,enable warnings, -Wall -full-wa
Do not hold your breath, since I need to get a PhD, but it occurs to me that
GUI independence would be accelerated by having some common cases as re-usable
widgets or something spiritually similar. How many boxes have a message and
yes, no and cancel buttons? Would it not make sense to have a g
This almost sounds like emacs outline mode which, as far as I have read the
manual, makes paragraph of lower section level than n invisible. You can
expand everything, just individual sections and so forth. I guess apporpiate
code hacks would allow lyx to do the same (replace the not shown par
OK, Try the following (including the spaces, which are required)
\def\ip2#1{{\catcode` =11\input{#1}\catcode` =10}}
and I think you will find that \ip2{foo bar baz.tex} will without any trouble.
The best effect can be had by putting that definition in the preamble. The
same approach can be ap
> On 1 Oct, Allan Rae wrote:
> I understood you perfectly. I do think (hope) that XML will become a
> standard, let us hope that that happens real soon. Until then, maybe
> we could have a M$ Word importer/exporter.
>
Modulo some major limitations word2x, catdoc or MSWordview might do the j
While it is not directly related to LyX yet, word2x is looking for CVS hosting
and in the running to become LyX's M$ word import facility (it is not there
quite yet, IMHO). Even if word starts using XML it will probably be littered
with physical style stuff that needs rewriting as a proper str
word2x is so named because it is supposed easy to add other formats. One could
add a LyX output end fairly easily and I will take responisbility for porting
it to word2x 2.0 when that is ready. It would be enough of a feature to
trigger a new release :-) I am not familar enough with .lyx forma
According to my man page strcasecmp is conforming to BSD 4.3 (and all unicies
I have seen so far, inclduign SunOS). AFAIK GNU libc 2.1 is conforming to ANSI
and POSIX but also includes common extensions, like mmap, lstat, setrlimit,
snprintf, select, fileno, *BSD sockets and whole bunch of oth
RTF is an excellent solution to the word to something else, inclyding LyX,
problem. Not only does it support practically everything bar macro virii but
it is also documented and reasonably sensible (quite a contrast with Word
binary format, which is subject to NDAs and baroque to put it mildly
Actually the latest version of word2x is 0.005. Asking for support for any
previous version is a little futile---I only want to hear about bugs that I
have not yet fixed. The website has moved to http://word2x.alcom.co.uk, so the
changes are no www and a different ISP name (actually the same p
word2x may be a better bet as it has structure extraction logic and has
mutiple backends (so you could put a LyX backend on it). Minimal OLE support
is likely to appear quite soon. The next major release of word2x will feature
configurable, modular, structure grinding stages. If anyone wants t
Actually there is another problem that the patches so far do not fix: view ps
will crop it to whatever it thinks the paper size actually is anyway and this
is a gs feature :-) This got me and my print queue---gs thought US letter and
depidated my A4 documents badly. The fix is to add -sPAPERSI
Arnd Hanses posted:
>
> Provided, box isn't too modern. New vendor patches (or new glibc) break
> configure tests, 'till someone is so kind as to provide the fix (which
> in turn breaks other tests, elsewhere, etc.)
>
Sort of strange... I have used linux since 0.99pl13, libc 4 (the old a.out
If it would help I am close to a LaTeX tokeniser close to the one described in
the TeXbook (Knuth). I figured mathed need it and could send a copy to an
interested developer for bug flattening and use elsewhere. It could surely
squash problems with reading filenames wiht a few newliines and sp
If xforms bugs get too serious then I have some source code which means I
could affect a fix. Distribution is a major problem---since source is not
normally
avialable patches are no good and I probably should not pass the source around
in random directions. I would says lack of a source distri
This would be possible with a little bit of TeXnical magic which changes %
into an active character and defines an appropiate macro. Any thought on what
they should look like? It might take a little care to ensure it works
absolutely
as we would like but this should not be a major change to Ly
mathed's lexer has some really stupid hacks in it. Following TeX on what is a
macro makes the code *much* simpler and would eliminate even more if I could
rebuild math_hash.C (the CVS sources seem to lack to input to gperf). All the
change required is to put the first character after the \ in
I am not sure whether this bug is a reLyX or mathed bug (argiably both
I guess). mathed segfaults in mathed_parse when attempting t o cope
with
\begin_inset Formula \[ T'=\left(
\vcenter{\hbox{
\valign{\vfil\hbox{\(\bsn#\)}\vfil&\vfil\hbox{\(\bsn#\)}&\vfil\hbox{\(\bsn#\)}\vfil\cr
I_{k'} & M' &
If it is properly structured document and word 8/97 format then mswordview
will produce a well structured HMTL version, which presumably will generate a
nice LyX version via hmtl2latex and relyx. If these conditions do not aplly
then it may be better to try mswordview's "competition" which do
Hmm... would it make sense to copy or otherwise arrange to have a paragraph
subject to mangling in a larger buffer split into two pieces (before and after
the cursor)? This is very efficient for insertations and deletions
anywhere---all it takes is adjusting a pointer and nothing special appli
79 matches
Mail list logo
