Re: New Windows version
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > It is also possible to build with the MS compiler (did anyone try that > recently?) Using the commercial version, perhaps. It is not possible to build Qt with the *free* version due to the lack of the delayimp.lib library. However I succeeded in building a native version of both Qt and LyX using the cygwin tools. When using the switch -mno-cygwin, the cygwin compilers turn into mingw compilers. -- Enrico
Re: copying and pasting a LyX environment? (like Word's Format Painter)
On Tue, Jan 10, 2006 at 02:26:48PM +0100, Abdel wrote:
> >This functionality could be implemneted in the Navigate menu in the
> >Qt frontend: Make the menu a list view, allowm multiple selection,
> >create and connect actions to movce things a level in or out.
>
> I was thinking about modifying the TOC dialog to do exactly this: allow
> moving a section and all it's dependencies to any upper or lower node
> you want. The TOC could even become a dock widget on the left "a la
> MSWord" and allow on-the-fly updating. Do you reckon the Navigate-Menu
> code is cleaner for this?
The current Navigate menu?
I'd think this is pure GUI stuff and should only call a few (new)
LFUNs (section-depth-{in,de}crease or similar) working on a selection
or something.
> >Could be extended to shift whole sections up and down.
>
> I guess we could re-use cut&paste for this, couldn't we?
Probably, yes. But c&p is close to the dirty corners in LyX, so
'obvious' stuff might not be implemnetable as easy as it looks.
> >Less than 200 lines for the in/out part I'd bet.
>
> Once you know what to do, it's always short to implement it ;-)
It usually is ;-}
Andre'
Re: idiosyncrasies with lyx and beamer (bookmarks)
Micha Feigin wrote:
On Thu, 29 Dec 2005 21:45:19 -0500
"Paul A. Rubin" <[EMAIL PROTECTED]> wrote:
Micha Feigin wrote:
For some reason when I use beamer with lyx and set tocdepth to 1 I get no
bookmarks for sections/subsections but setting it to 2 I get bookmarks for both
sections and subsections.
This doesn't match the latex behavior which is one behind (sections only in
bookmarks for tocdepth=2 and nothing for tocdepth=1)
Any idea on what lyx is doing different between view and export for this or how
to check?
Could be a bug in Beamer? You might try reporting it on the Beamer help
forum and see if anyone knows about it (or just submit a bug report).
There seems to be a bug in beamer (I though it was hyperref but it seems to be
a problem with beamer 3.06) but there is also something that lyx is not doing
right since with tocdepth=2 its producing the right output although exporting
to latex and compiling results with a buggy output, with tocdepth=1 compiling
through lyx and exporting to latex do the same thing.
The conclusion is that lyx compiles itself something else then what it exports
to latex.
I think the problem has something to do with LyX using outdated
intermediate files in the temp directory. I experimented with a simple
beamer file in which I put \setcounter{tocdepth}{whatever} in ERT in a
standard paragraph between the title slide and the TOC frame. If I set
tocdepth to 1, exported a .tex file and ran pdflatex against it, I
consistently go no bookmarks and sections only in the TOC. On the other
hand, if I did View->PDF (pdflatex), I got sections only in the TOC, but
the bookmarks were either empty, sections or sections + subsections (!),
depending I think on what values of tocdepth I had most recently tried.
I reproduced that last output using export to .tex as follows. I set
tocdepth to 3, exported to .tex and ran pdflatex twice. I got
(correctly, I think) both sections and subsections in the bookmarks and
in the TOC. (The file did not have subsubsections.) Then I changed
tocdepth to 1 in the LyX document, exported again, and ran pdflatex only
once. The resulting file had sections but not subsections in the TOC,
but had subsections in the bookmarks. When I ran pdflatex the second
time, the TOC retained sections but the bookmarks disappeared.
So I'm guessing LyX sometimes runs pdflatex only once (?).
/Paul
Re: International characters in file names - Lyx 1.4pre3, MacOSX
Georg Baum Fri, 13 Jan 2006 08:49:27 -0800 Anders Ekberg wrote: > I know that spaces and international characters have been discussed > as issues before. Are these problems supposed to be solved in version > 1.4? No. As usual, if you want that to change, report it in bugzilla, but it will probably be low priority. In this case OS and frontend information is essential. I am not sure whether this is a LyX problem at all, it may well be a bug or missing feature in the underlying OS or qt library. Georg I guess it is perhaps better to leave it for now (with all the focus being on rolling out 1.3.7 and 1.4). Perhaps it may solve itself with QT4.1. In the mean time it would be good if it was possible to implement a more descriptive error message since the problem is fairly easy to overcome for a user if he/she knows what causes it. /Anders
Re: Why does my text runneth into the right margin?
Roy Schestowitz writes: > You have just helped me solve a recurrent problem that I last > experienced yesterday. I am getting this too and often I fail to > spot it before sub- mitting papers Add "draft" to the Options in the Layout menu -- you won't miss them anymore (unless your article is about large black boxes!). -Kevin -- Kevin Pfeiffer <[EMAIL PROTECTED]> Tiros-Translations
Re: "no-hyphenation point"? [answer: \nobreakdash]
Kevin Pfeiffer writes: > Or... > > Insert -> Special Character -> Dash Protector (insert before dash) Working (and looking like) the "Ligature Break"... -Kevin (I know, "Bugzilla") -- Kevin Pfeiffer <[EMAIL PROTECTED]> Tiros-Translations
Re: Why does my text runneth into the right margin?
_/ On Thu 12 Jan 2006 08:56:20 GMT, [Georg Baum] wrote : \_
Martin Geisler wrote:
If the word occurs several times you might want to simply extrend the
hyphenation knowledge of TeX by saying
\hyphenation{foo-bar}
in your Preamble. This it will take effect for all foobars.
If it does not, read this: http://bugzilla.lyx.org/show_bug.cgi?id=1503
Georg
You have just helped me solve a recurrent problem that I last experienced
yesterday. I am getting this too and often I fail to spot it before sub-
mitting papers (LaTeX, not LyX due to imposed templates). I finally under-
stand what \hyphenation{} is intended to achieve. It's often at the top
to serve as a placeholder.
Margin issues can only be detected by the eye if you specifically aim to
identify it. If only I got a warning prominent enough while compiling...
Thanks,
Roy
Re: New Windows version
> "Abdel" == Abdel <[EMAIL PROTECTED]> writes: Abdel> Hum, right now it's impossible to build 1.4cvs with mingw Abdel> because of automake change. Thanks god I haven't reconfigured Abdel> since before the change. AFAIK, the only solution would be to Abdel> deliver source snapshot with already generated Makefiles. Maybe Abdel> it is already available somewhere? It is also possible to build with the MS compiler (did anyone try that recently?) JMarc
Re: New Windows version
Lars Gullik Bjønnes a écrit : Abdel <[EMAIL PROTECTED]> writes: | Helge Hafting a écrit : | > Lars Olesen wrote: | > | >> When is the windows version of lyx 1.4 expected. I need it to make | >> some exams now :) | >> | > If you really need lyx 1.4 quickly - check out the source and | > compile it yourself. | > I've been using it for half a year, on linux. | > Helge Hafting | | Hum, right now it's impossible to build 1.4cvs with mingw because of | automake change. Hmm... I do not remember seeing a report about that. Angus reported it but I have to admit that I didn't even tried... http://article.gmane.org/gmane.editors.lyx.devel/51211/match=automake+1+9+mingw
Re: International characters in file names - Lyx 1.4pre3, MacOSX
Anders Ekberg wrote: > I know that spaces and international characters have been discussed > as issues before. Are these problems supposed to be solved in version > 1.4? No. As usual, if you want that to change, report it in bugzilla, but it will probably be low priority. In this case OS and frontend information is essential. I am not sure whether this is a LyX problem at all, it may well be a bug or missing feature in the underlying OS or qt library. Georg
Re: International characters in file names - Lyx 1.4pre3, MacOSX
> "Anders" == Anders Ekberg <[EMAIL PROTECTED]> writes: Anders> I know that spaces and international characters have been Anders> discussed as issues before. Are these problems supposed to be Anders> solved in version 1.4? Not really. Only spaces work better. JMarc
Re: "no-hyphenation point"? [answer: \nobreakdash]
On Fri, 13 Jan 2006, Kevin Pfeiffer wrote:
My LaTeX Companion book arrived today (hurrah) and looks to be useful.
In it, for example, I found an answer to the (correct) question above:
In Preamble: \usepackage{amsmath}
Command: \nobreakdash (goes in an ERT)
Glad you found it, Kevin. I looked in the index of TLC2 but must have had
improper search terms.
Rich
--
Richard B. Shepard, Ph.D. | Author of "Quantifying Environmental
Applied Ecosystem Services, Inc. (TM) | Impact Assessments Using Fuzzy Logic"
Voice: 503-667-4517 Fax: 503-667-8863
Re: "no-hyphenation point"? [answer: \nobreakdash]
Kevin Pfeiffer writes:
> I have a paragraph that speaks literally an "-ism" and it was
> breaking like this:
> --
> Under no circumstances should it end in -ismus or -
> ism, or -isten.
> ---
>
> I fixed this by placing "-ism" in a \makebox{}, but was wondering if
> there might be a simpler or a LyX way (not that this was complicated,
> but thought there might be an "Insert -> Special Character ->
> Protected Break" or "No-Hyphenation Point"...
My LaTeX Companion book arrived today (hurrah) and looks to be useful.
In it, for example, I found an answer to the (correct) question above:
In Preamble: \usepackage{amsmath}
Command: \nobreakdash (goes in an ERT)
Examples:
"Pages 3\nobreakdash--9 are to be read."
"He's a five\nobreakdash-time winner!"
This is so simple that perhaps it could be added to the Special
Characters menu?
Insert -> Special Character -> Non-Breaking Dash -> Hyphen, En-Dash,
Em--Dash (in drop-down)
Or...
Insert -> Special Character -> Dash Protector (insert before dash)
Bye,
Kevin
--
Kevin Pfeiffer <[EMAIL PROTECTED]>
Tiros-Translations
Re: New Windows version
- Original Message - From: ""Lars Gullik Bjønnes"" <[EMAIL PROTECTED]> To: Sent: Friday, January 13, 2006 6:02 AM Subject: Re: New Windows version Abdel <[EMAIL PROTECTED]> writes: | Helge Hafting a écrit : | > Lars Olesen wrote: | > | >> When is the windows version of lyx 1.4 expected. I need it to make | >> some exams now :) | >> | > If you really need lyx 1.4 quickly - check out the source and | > compile it yourself. | > I've been using it for half a year, on linux. | > Helge Hafting | | Hum, right now it's impossible to build 1.4cvs with mingw because of | automake change. Hmm... I do not remember seeing a report about that. -- Lgb Angus wrote: Subject: No automake-1.9 on mingw/msys yet "As things stand, I'm afraid that the port of automake 1.9 to Windows isn't yet ready for prime time. (Hence it isn't part of MSYS yet). That means I can build neither LyX 1.4 nor tex2lyx on Windows using mingw/msys. (This is with an otherwise pristine source tree.)" http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg84507.html Michael Gerz <[EMAIL PROTECTED]> writes: I also noticed that MinGW no longer allows you to build 1.4.0cvs. As a workaround, I use cygwin's automake to generate the Makefiles. It works as expected but, of course, it isn't nice to have to install and use cygwin in addition to MinGW. Thank god, we ship the final 1.4.0 source distribution with the auto-generated files so that the users do not have to run automake by themselves. A MinGW version of both Qt and LyX can be built by using the cygwin g++ with the -mno-cygwin switch. If there is interest I'll post my howto. It is not for the faint-heart, though ;-) -- Enrico -- Regards, Stephen
Re: New Windows version
Abdel <[EMAIL PROTECTED]> writes: | Helge Hafting a écrit : | > Lars Olesen wrote: | > | >> When is the windows version of lyx 1.4 expected. I need it to make | >> some exams now :) | >> | > If you really need lyx 1.4 quickly - check out the source and | > compile it yourself. | > I've been using it for half a year, on linux. | > Helge Hafting | | Hum, right now it's impossible to build 1.4cvs with mingw because of | automake change. Hmm... I do not remember seeing a report about that. -- Lgb
International characters in file names - Lyx 1.4pre3, MacOSX
Under Lyx1.4pre3 on Mac OSX 10.4, saving a file with an international character (e.g. ö [i.e. ö] or cyrillic letters) in the filename gives a message that the file already exists (attempt to overwrite of course fails). If the international character is in the path name the message is that the file cannot be saved. Spaces in filenames and pathnames work fine, though. I know that spaces and international characters have been discussed as issues before. Are these problems supposed to be solved in version 1.4? Anders Ekberg
Re: New Windows version
- Original Message - From: "Abdel" <[EMAIL PROTECTED]> To: Sent: Friday, January 13, 2006 4:40 AM Subject: Re: New Windows version Helge Hafting a écrit : Lars Olesen wrote: When is the windows version of lyx 1.4 expected. I need it to make some exams now :) If you really need lyx 1.4 quickly - check out the source and compile it yourself. I've been using it for half a year, on linux. Helge Hafting Hum, right now it's impossible to build 1.4cvs with mingw because of automake change. Thanks god I haven't reconfigured since before the change. AFAIK, the only solution would be to deliver source snapshot with already generated Makefiles. Maybe it is already available somewhere? Abdel. ftp://ftp.devel.lyx.org/pub/lyx/pre/lyx-1.4.0pre3.tar.gz ftp://ftp.devel.lyx.org/pub/lyx/pre/lyx-1.4.0pre3.tar.bz2 Lgb Before pre3 I used Michael Gerz' instructions to compile LyX1.4.0 cvs which are fairly involved. I was able to install lyx1.4.0pre3 though, without any file editing, just docs: Install_Win32, build_lyxwin.sh and package_lyxwin.sh. It took a fair amount of disk space and memory. This worked though it took awhile even though I linked statically. I did not try the cvs after this because I read about automake. The improved official 1.3.7 version is due out Monday (maybe Tuesday). Best regards, Stephen
Re: New Windows version
Helge Hafting a écrit : Lars Olesen wrote: When is the windows version of lyx 1.4 expected. I need it to make some exams now :) If you really need lyx 1.4 quickly - check out the source and compile it yourself. I've been using it for half a year, on linux. Helge Hafting Hum, right now it's impossible to build 1.4cvs with mingw because of automake change. Thanks god I haven't reconfigured since before the change. AFAIK, the only solution would be to deliver source snapshot with already generated Makefiles. Maybe it is already available somewhere? Abdel.
Re: sixth release of LyXWinInstaller
- Original Message -
From: "Helge Hafting" <[EMAIL PROTECTED]>
To: "Bo Peng" <[EMAIL PROTECTED]>
Cc: ; "LyX Devel"
Sent: Thursday, January 12, 2006 11:48 PM
Subject: Re: sixth release of LyXWinInstaller
The best fix is to have tex fixed. Second best is lyx providing
a workaround. Either approach needs a volunteer - I wonder
why nobody seems to want to fix tex though.
Helge Hafting
http://groups.google.com/group/comp.text.tex/msg/6d9312da816b96f7?hl=en&;
Dan Luecking wrote:
"TeX has been designed with a basic command \input. Normally it takes a
space as ending the name. MiKTeX amends this to allow spaces if the
name is (double) quoted. On the otherhand, some tools used with TeX
don't like spaces. If a chain of tools is invoked, quotes may get
stripped, and if even one tool does this (batch files processing can
do this) then later tools in the chain, even space-aware tools,
will fail. ...
Microsoft was just showing off when it named system default
directories with spaces. This already makes it confusing to read
Environmental variables. It forces additional levels of filename
processing in programs (check for quotes around flenames, add them
only if not already there. Try to program batch files for all the
cases.) I'm sure Microsoft is intentionally trying to make it
hard for Unix-style tools to work in Windows."
--
SH: To me, Dan seems like a reliable supplier of information.
TeX was invented around 1982 and didn't run on Windows.
Leslie Lamport writes:
"In the early 80s, I was planning to write the Great American Concurrency
Book. I was a TeX user, so I would need a set of macros. I thought that,
with a little extra effort, I could make my macros usable by others. Don
Knuth had begun issuing early releases of the current version of TeX, and
I figured I could write what would become its standard macro package. That
was the beginning of LaTeX. I was planning to write a user manual, but it
never occurred to me that anyone would actually pay money for it. In
1983,"...
SH: Maybe Win95 had paths with spaces. Win98 had paths with spaces
which needed to be double quoted ("blah blah blah"). WinXP works
quite well with spaces. My point is that TeX was designed to work the
way it does, it is not a bug. I don't think TeX would be easy to fix and
retain compatibility with earlier files. Should the next word of input after
a space part of the filename/path or when TeX usually begins operation?
I've also read that \includegraphics used to have a problem with paths with
spaces. Angus says this was fixed and he says bibtex/natbib has not been
fixed yet. I am not so sure that a Miktex/ProTeXt developer is going to
see this as a problem/bug with Miktex. I've been reading about the hassle
of integrating Auctex-preview into Xemacs. The Linux world doesn't take
responsibility for fixing smaller packages that work with their big package,
or even go so far as to make it easy to include them.
Helge wrote: > The best fix is to have tex fixed.
SH: Perhaps you can understand my doubt that this is a viable or
even optimal solution, considering backward compatibility.
Helge wrote: > Second best is lyx providing a workaround.
SH: Not trying to be contentious, but this seems first best to me.
And better than the error message idea. How important is fixing this?
I do think it has some value; I'm not disputing that.
--
Best regards,
Stephen
Re: sixth release of LyXWinInstaller
On Fri, 13 Jan 2006 08:48:09 +0100 Helge Hafting <[EMAIL PROTECTED]> wrote: > Bo Peng wrote: > > >>Guys, I'm amazed that this thread has gone on as long as it has. I'm going > >>to pop my head in at the door one final time and will then leave you to > >>play on your own again. > >> > >> > > > >I am amazed as well, in that many people even do not consider this as > >a bug. A bug report has been created > >(http://bugzilla.lyx.org/show_bug.cgi?id=2186) and accepted as NEW so > >we should just wait for someone (Andre? Georg?) to fix it. > > > > > > > Feel free to call it a bug - but the bug is not in lyx so an entry in > bugzilla.lyx.org is wrong. latex/bibtex is where the bug is, > and they have a different forum. > > >I would also like to leave this thread with some final remarks. > > > >The root of this problem is of course from latex/bibtex and if a > >normal user really knows latex, has read all the documentations (lyx > >and latex), he should not put a .bst file under a path with spaces > >(and be considered as pro-user :-). However, most lyx users do *not* > >know latex that well and the goal of lyx is exactly to provide a > >user-friendly GUI to latex to allow such users to use latex easily. We > >have successfully circumstanced similar problems with .lyx, .bib, > >.eps etc, why not .bst files? > > > >Regarding whether or not this is a lyx bug, I would definitely say yes > >in recognition of the fact that lyx allows certain user input and > >produces defective output without warning. > > > You think it'd be better if lyx simply refused, saying "no, > I can't use that .bst file, because it happens to be in a > path with spaces so bibtex is going to choke on it" ? > > There is one reason why that would be a bad move, bibtex > might get fixed into accepting paths with spaces someday, and then > lyx would be protection against a bug that no longer exist. Then > lyx would need to be fixed again. > IIRC that was the state of things back when windows lyx couldn't handle spaces in the path to files. > The best fix is to have tex fixed. Second best is lyx providing > a workaround. Either approach needs a volunteer - I wonder > why nobody seems to want to fix tex though. > > Helge Hafting > > +++ > This Mail Was Scanned By Mail-seCure System > at the Tel-Aviv University CC. > +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC.
