Re: Number of LaTeX runs
Jean-Marc Lasgouttes wrote: > The question is to know what happens when there is a faulty reference > in the file. We cannot run latex until there is n more error. This is > why the package should output a message like what normal references > do. We only rerun LaTeX once, then we proceed with BibTeX, Makeindex etc. Faulty references are resolved at a later stage, when the "unresolved reference" messages are considered. Jürgen
Re: Using movie15 with LyX to insert movies in PDF output
Hello, Sorry i deleted the first mail so maybe I will not give a proper reply. My opinion is that you cannot generate a pdf file from a latex file containing movie15 commands using lyx. You can use lyx to export the latex code and then you will have to use the technique specified in the movie15 documentation. At least that's the way I did it!> Gerard Ateshian ha scritto: > > pdfTeX error (ext5): cannot open file for embedding. > > I think that when you ask LyX to generate the pdf a latex file is > generated somewhere in /tmp/lyx_*, and it is passed through pdflatex > directly there. > > As LyX doesn't know that you are including the movie it cannot make a > copy (or a link) from the file to the temporary location. > > You can try to copy the movie file by hand in the temporary location, or > some similar workaround. > > -- > Lorenzo `paulatz' Paulatto > Trieste > > ``Grandissima mi par l'inezia di coloro che vorrebbero che Iddio avesse > fatto l'universo più proporzionato alla piccola capacità del lor discorso.'' > --Galileo Galilei (Opere VII) > > > -- > Email.it, the professional e-mail, gratis per te: http://www.email.it/f > > Sponsor: > Raggruppa i tuoi finanziamenti in uno: pagherai ununica rata fino al 50% > più bassa della tua attuale! Clicca qui e chiedi maggiori informazioni a > Prometeo! > * > Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=7433&d=16-1 >
Re: Number of LaTeX runs
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: >> The question is to know what happens when there is a faulty reference >> in the file. We cannot run latex until there is n more error. This is >> why the package should output a message like what normal references >> do. > > We only rerun LaTeX once, then we proceed with BibTeX, Makeindex etc. Faulty > references are resolved at a later stage, when the "unresolved reference" > messages are considered. OK then. JMarc
Re: Number of LaTeX runs
Jean-Marc Lasgouttes wrote: > OK then. Committed. Tobias, LyX 1.5.4 is supposed to handle the clefval case correctly. Jürgen
Re: LyX Qt under Gnome environment
On Wednesday 16 January 2008 05:17:48 Raymond Ouellette wrote: > p.s. If necessary, I can upload my deb package of LyX 1.5.3 for the ftp >site. I have a question partially related to your post. I am using Ubuntu 7.10, and I cannot install LyX using Synaptic (the package installation system of Ubuntu) because I have a TeXLive in stallation, installed from the CD, and the paths are not the same of the Ubuntu installation; so if I try to install from Synaptic, the animal complains saying that it will also install TeX, which will mess up all the TeXLive paths (already tried, a whole evening lost uninstalling and in stalling again TeX). Also the debian installer tries to do the same. Questions: (1) is compilation on Ubuntu difficult? I thinks that compiling and installing manually should avoid the problem I mentioned; (2) if (1) is not practical, can anyone suggest all the symlink that I should set up to persuade Synaptic that I have already a TeX system running? Many thanks, guido milanese, italy -- http://docenti.unicatt.it/milanese_guido http://www.arsantiqua.org
Incoming 1.5.3 binaries for debian/ubuntu distributions
Hi, Available LyX 1.5.3 checkinstall packages for *etch* and *dapper* on ftp.devel.lyx.org/pub/incoming/ lyx_1.5.3-1_i386_dapper.deb lyx_1.5.3-1_i386_etch.deb lyx_1.5.3_i386_dapper.README lyx_1.5.3_i386_etch.README Could someone please move them to the appropriate place. Many thanks! Cheers, Sam
Re: [OT] Best KDE-centric Distribution?
Charles de Miramon wrote: rgheck wrote: Debian Etch. [snip] Thanks for the suggestion. I've thought about Debian, and it has a great reputation for stability. That said, while I don't want to be absolutely bleeding edge, I do like to be near it, and Debian at least has a reputation for being, well, stable. Just looking at the packages, it looks like Lyx 1.4.3 is the most recent in etch. It looks as if lenny has 1.5.2, but even that's out of date, and, as you say, that's not yet ready. So, well, I'm still looking. Richard Debian unstable (that I use) has 1.5.3. Unstable is not so unstable because most big transformations happens in "experimental". I run a mix of debian unstable and debian testing. Testing is more stable, as stuff in unstable migrate to testing only when it had 2 weeks in unstable without getting bug reports. So testing is mostly up to date, althoug bugs sometimes holds up stuff. In those cases I sometimes install the unstable stuff anyway, if the bug in question doesn't bother me. You can set up debian so it fetches software packages from both testing and unstable (and experimental, if you dare), and give "testing" priority. You can then get packages from unstable or experimental by explicitly asking for the higher version numbers for those. You may track "stable" too, it is then possible to revert troublesome packages back to known good status. Helge Hafting
Re: (latex question) Repeated footnote?
Daniel CLEMENT wrote: Also possible : Place the cross-reference to the labeled footnote in a superscript, so that it will appear as a note too. Thus you get twice the same reference to the same footnote, they look alike, and the numbering si preserved. Be careful if your footnotes are set up to reset on every new page. Because a page break could happen between two references to the same footnote. The next page might then have a different footnote re-using the same footnote number. Not a problem if your footnote numbers increase all the way, (or reset only per-chapter), or if you use the "see footnote x on page y" form of reference. Helge Hafting
Re: left justify floats?
bigblop wrote: Hm it seems that I cannot include a pdf file even though it get shown in the pdfpreview. I get the error: "Error converting to loadable format" in LyX. When I press the edit button after clicking on the float I get: No information for editing PDF (ps2pdf) Is it not possible to include PDF in LyX files? Yes - you can include PDF when you're using pdflatex for producing output. Some of the external insets will even be included as pdf files when pdflatex is used. This doesn't work with printing, because printing produces output in a different manner. The workaround is simple, export->pdf and then print the pdf file itself. I was hoping for a preference setting that allows printing via pdflatex instead of the usual way, because that is necessary for using microtype. But lyx currently doesn't support microtype directly so there is "no need". . . Helge Hafting
Re: Using movie15 with LyX to insert movies in PDF output
Hi Bruno, It turns out it is possible to use LyX with movie15 (see earlier responses by Lorenzo and JMarc), with the caveat that the full path to the movie file must be provided. One must also use a PDF viewer that can display movies (such as Acrobat Reader 8) as the default viewer in LyX. Gerard On Jan 17, 2008, at 4:03 AM, Bruno C. wrote: Hello, Sorry i deleted the first mail so maybe I will not give a proper reply. My opinion is that you cannot generate a pdf file from a latex file containing movie15 commands using lyx. You can use lyx to export the latex code and then you will have to use the technique specified in the movie15 documentation. At least that's the way I did it!> Gerard Ateshian ha scritto: pdfTeX error (ext5): cannot open file for embedding. I think that when you ask LyX to generate the pdf a latex file is generated somewhere in /tmp/lyx_*, and it is passed through pdflatex directly there. As LyX doesn't know that you are including the movie it cannot make a copy (or a link) from the file to the temporary location. You can try to copy the movie file by hand in the temporary location, or some similar workaround. -- Lorenzo `paulatz' Paulatto Trieste ``Grandissima mi par l'inezia di coloro che vorrebbero che Iddio avesse fatto l'universo più proporzionato alla piccola capacità del lor discorso.'' --Galileo Galilei (Opere VII) -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Raggruppa i tuoi finanziamenti in uno: pagherai un’unica rata fino al 50% più bassa della tua attuale! Clicca qui e chiedi maggiori informazioni a Prometeo! * Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=7433&d=16-1
Re: Incoming 1.5.3 binaries for debian/ubuntu distributions
Sven Hoexter wrote: > > Available LyX 1.5.3 checkinstall packages for *etch* and *dapper* on > > ftp.devel.lyx.org/pub/incoming/ > > Sam please don't take it as an offense but I'd highly recommend to not > use those checkinstall packages for Debian/etch. The same reasoning > apply for Ubuntu so you might want to read on as an Ubuntu user aswell. I just uploaded them to ftp.lyx.org. So what now? Jürgen
Re: Incoming 1.5.3 binaries for debian/ubuntu distributions
On Thu, Jan 17, 2008 at 11:41:42AM +, Sam Lewis wrote: Hi Sam, hi all, > Available LyX 1.5.3 checkinstall packages for *etch* and *dapper* on > ftp.devel.lyx.org/pub/incoming/ Sam please don't take it as an offense but I'd highly recommend to not use those checkinstall packages for Debian/etch. The same reasoning apply for Ubuntu so you might want to read on as an Ubuntu user aswell. I'd like to see packages on backports.org but that doesn't seem to happen in the short term so instead of installing some checkinstall packages from an unknown source (my parents always told me to not take food from stranges, it's in some way similar to this case or do you like to give Sam your root passwort?) you could use a backport provided by Emilio Scalise. http://emiscabpo.wordpress.com/about/ Sure I can not prove if the binary packages were really build from the source packages in the same repo but at least there is a sane source package provided along with the binary packages and the binary packages have sane dependencys and version numbers. One backdraw is that you're forced to migrate to texlive from tetex if you're still using tetex. This will happen with lenny anyway but it will force you to download a few hundred MiB of texlive packages along with the new LyX and boost packages. Emilio: If you could change the texlive deps to texlive|tetex stuff (maybe take a lock at my bpo proposed packages) and maybe change the version extension to not look like backports.org (because they seem to not end up there) they would be my recommendation for Debian/etch users with a demand for LyX 1.5.x packages. Sven -- There's no need for tears, cause there's no need to cry. That love that you leave will never be denied. [ Flogging Molly - Laura ] Gebuehrenboykott 2008 BU WTAL http://www.boykott-wuppertal.de signature.asc Description: Digital signature
BibTex force Lyx to crash :-(
Hello everybody, this is not a bug... is a problem concerning my bibtex file... or installation but I can't understand how to fix it :-( Ok, let's start from beginning. I use lyx for creating my documents on Linux (OpenSuse 10.2) and I use a bib file for my references. All goes ok. Some day ago, I buyed a Mac... and I'm moving all my work stuff on Mac. I installed MacTex... and LyX 1.5.3 When I open a document created by me that use the .bib file... and I generate the .pdf (pdflatex)... Lyx crash with reporting the following lines on debug console: - Running BibTeX. - We got a translation - terminate called after throwing an instance of 'boost::filesystem::basic_filesystem_errorboost::filesystem::path_traits> >' - what(): boost::filesystem::exists - Abort trap So, I guessed that is a problem of my bib file... and in fact, if I remove only the bibtex field and the end of document... Lyx will not crash and generate a perfect PDF ... but I can't understand why bibtex crash LyX... and what I have to do for fix it. Just for completeness, I'm italian and I run all in italian language. Thanks, Gianluca
lyx wiki problems
http://wiki.lyx.org/uploads/Tools/LyX2OpenOffice/ConvTex.zip doesn't exist. Is there a working ConvTex and if so where can I find it?
Re: lyx wiki problems
Neal Becker wrote: http://wiki.lyx.org/uploads/Tools/LyX2OpenOffice/ConvTex.zip doesn't exist. Is there a working ConvTex and if so where can I find it? Try http://wiki.lyx.org/uploads/Tools/LyX2OpenOffice/Previous%20Version/ConvTex.zip. Looks like a bunch of files were moved to a "Previous Version" folder. I would update the wiki page, but I don't know what to say (since I don't know to what "previous version" refers). /Paul
Re: BibTex force Lyx to crash :-(
G. Massera wrote: Hello everybody, this is not a bug... is a problem concerning my bibtex file... or installation but I can't understand how to fix it :-( Ok, let's start from beginning. I use lyx for creating my documents on Linux (OpenSuse 10.2) and I use a bib file for my references. All goes ok. Some day ago, I buyed a Mac... and I'm moving all my work stuff on Mac. I installed MacTex... and LyX 1.5.3 When I open a document created by me that use the .bib file... and I generate the .pdf (pdflatex)... Lyx crash with reporting the following lines on debug console: - Running BibTeX. - We got a translation - terminate called after throwing an instance of 'boost::filesystem::basic_filesystem_errorboost::filesystem::path_traits> >' - what(): boost::filesystem::exists - Abort trap So, I guessed that is a problem of my bib file... and in fact, if I remove only the bibtex field and the end of document... Lyx will not crash and generate a perfect PDF ... but I can't understand why bibtex crash LyX... and what I have to do for fix it. Well, if LyX is crashing, that is a problem, whatever else is happening. First, try exporting to LaTeX and running, from a terminal: >latex yourfile >bibtex yourfile >latex yourfile >latex yourfile Report any error messages you get. After that, one of us should have a look at the file and see if we can reproduce the crash. Can you get it to do it with just the bibtex field? Richard
Re: LyX Qt under Gnome environment
Questions: (1) is compilation on Ubuntu difficult? I thinks that compiling and installing manually should avoid the problem I mentioned; It shouldn't be. You just need to make sure you have the qt-devel packages, I think. but you'll see when you run ./configure if you have problems. (2) if (1) is not practical, can anyone suggest all the symlink that I should set up to persuade Synaptic that I have already a TeX system running? I think it uses a database of installed packages to resolve dependencies. But you might be able to force the install. I know you can do this with rpm, using the --nodeps switch. rh
Re: BibTex force Lyx to crash :-( [SOLVED]
In fact, I think that if I pass my lyx document to a my friend ... without the .bib.. lyx will crash :-( :-( If I create a file with a missing .bib file, I don't get a crash. So it must be more than that. rh
Re: Incoming 1.5.3 binaries for debian/ubuntu distributions
Sven Hoexter <[EMAIL PROTECTED]> writes: > Sam please don't take it as an offense but I'd highly recommend to not > use those checkinstall packages for Debian/etch. The same reasoning > apply for Ubuntu so you might want to read on as an Ubuntu user > aswell. Hi Sven, Thank you for your concern! To clarify these are not official packages, but made available by me for other LyX users, on debian-based distros, who don't want to wait until official releases included these versions. I've provided packages for several years and there have been no complaints. They are built on non-modified releases of etch and dapper and by reading the README file (that are also uploaded) one gets a good idea about build dependencies. If 1.5.3 is is already available on backports.org that's great, and my packages are not be needed then. If not, than responsible users might choose to uses these. > One backdraw is that you're forced to migrate to texlive from tetex > if you're still using tetex. This will happen with lenny anyway but > it will force you to download a few hundred MiB of texlive packages > along with the new LyX and boost packages. There are no tex-distro decencies set on my packages, one can uses whatever one likes. Indeed, I thought, it was in the very spirit of LyX, that some users provide there binaries for other users without predefining every interacting software. Cheers, Sam -- etch: Build information: ./configure --with-qt-dir=/usr/share/qt4 --enable-optimization=-O3 --prefix=/us r/local Configuration Host type:i686-pc-linux-gnu Special build flags: pch use-aspell use-ispell C Compiler: gcc C Compiler LyX flags: C Compiler flags: -O3 C++ Compiler: g++ (4.1.2) C++ Compiler LyX flags: C++ Compiler flags: -O3 Linker flags: Linker user flags: Qt 4 Frontend: Qt 4 version: 4.2.1 Packaging:posix LyX binary dir: /usr/local/bin LyX files dir:/usr/local/share/lyx make sudo checkinstall make install-strip dapper: Build information: ./configure --with-qt-dir=/usr/share/qt4 --enable-optimization=-O3 --prefix=/usr/local Configuration Host type:i586-pc-linux-gnu Special build flags: aiksaurus pch use-aspell use-ispell C Compiler: gcc C Compiler LyX flags: C Compiler flags: -O3 C++ Compiler: g++ (4.0.3) C++ Compiler LyX flags: C++ Compiler flags: -O3 Linker flags: Linker user flags: Qt 4 Frontend: Qt 4 version: 4.2.1 Packaging:posix LyX binary dir: /usr/local/bin LyX files dir:/usr/local/share/lyx make sudo checkinstall make install-strip
Re: BibTex force Lyx to crash :-( [SOLVED]
The problem is regarding the "/home/gianluca" access. In fact... if you create a simple document and you add a bibtex database... and after you edit the .lyx file outside lyx with a texteditor... and change the line bibfiles "/Users/gianluca/tmp/Articoli/databaseAll" with a line that try to access to "/home/" directory on Mac bibfiles "/home/gianluca/tmp/Articoli/databaseAll" It will crash. But if you change to another directory it will not crash even if the file doesn't exist. Maybe the problem could be in the fact that I can't even list the "/home/" directory on Mac In fact, on apple terminal this is what I get: Mac:~> ls /home/gianluca ls: /home/gianluca: Input/output error rgheck ha scritto: In fact, I think that if I pass my lyx document to a my friend ... without the .bib.. lyx will crash :-( :-( If I create a file with a missing .bib file, I don't get a crash. So it must be more than that. rh
Re: BibTex force Lyx to crash :-( [SOLVED]
Ok... I understand where was the problem. In my linux machine the database was in "home/gianluca/Documents/database.bib" ... but when I moved my Documents data... now on Mac the position is "Users/gianluca/Documents/dtatabase.bib" !!! I click on the bibtex field on Lyx... I removed the database pointing to "home/gianluca" and added the right one... and no more crash :-) But a question arise: "Why don't simply report that the file doesn't exist ... instead of getting crash ???" Maybe, a simple check before running bibtex would be nice to avoid this kind of problems. In fact, I think that if I pass my lyx document to a my friend ... without the .bib.. lyx will crash :-( :-( Cheers, Gianluca rgheck ha scritto: G. Massera wrote: Hello everybody, this is not a bug... is a problem concerning my bibtex file... or installation but I can't understand how to fix it :-( Ok, let's start from beginning. I use lyx for creating my documents on Linux (OpenSuse 10.2) and I use a bib file for my references. All goes ok. Some day ago, I buyed a Mac... and I'm moving all my work stuff on Mac. I installed MacTex... and LyX 1.5.3 When I open a document created by me that use the .bib file... and I generate the .pdf (pdflatex)... Lyx crash with reporting the following lines on debug console: - Running BibTeX. - We got a translation - terminate called after throwing an instance of 'boost::filesystem::basic_filesystem_errorboost::filesystem::path_traits> >' - what(): boost::filesystem::exists - Abort trap So, I guessed that is a problem of my bib file... and in fact, if I remove only the bibtex field and the end of document... Lyx will not crash and generate a perfect PDF ... but I can't understand why bibtex crash LyX... and what I have to do for fix it. Well, if LyX is crashing, that is a problem, whatever else is happening. First, try exporting to LaTeX and running, from a terminal: >latex yourfile >bibtex yourfile >latex yourfile >latex yourfile Report any error messages you get. After that, one of us should have a look at the file and see if we can reproduce the crash. Can you get it to do it with just the bibtex field? Richard
Re: Incoming 1.5.3 binaries for debian/ubuntu distributions
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > I just uploaded them to ftp.lyx.org. Thanks! Cheers, Sam
generic X copy-and-paste not working
Normally, I can highlight text in a terminal and paste it with a middle-click. In LyX, usually I can get to it with Edit -> Paste Special. (I can copy-and-paste fine in my xterms.) In my LyX, the Paste Special choices are shaded out and not clickable. This is LyX 1.5.2 on NetBSD. I am not running any clipboard utility. Any ideas why I can't paste into LyX?
Re: Incoming 1.5.3 binaries for debian/ubuntu distributions
Christopher Menzel wrote: On Jan 17, 2008, at 5:41 AM, Sam Lewis wrote: ftp Available LyX 1.5.3 checkinstall packages for *etch* and *dapper* on ftp.devel.lyx.org/pub/incoming/ lyx_1.5.3-1_i386_dapper.deb lyx_1.5.3-1_i386_etch.deb Are we to assume negation as failure here or are there already packages available for feisty and gutsy somewhere? So far, the only Ubuntu native package of 1.5.3 I've seen has been in the Hardy repositories - which has dependencies that Gutsy doesn't satisfy. (I haven't looked at backports.org yet) // George
Re: Incoming 1.5.3 binaries for debian/ubuntu distributions
On Jan 17, 2008, at 5:41 AM, Sam Lewis wrote: ftp Available LyX 1.5.3 checkinstall packages for *etch* and *dapper* on ftp.devel.lyx.org/pub/incoming/ lyx_1.5.3-1_i386_dapper.deb lyx_1.5.3-1_i386_etch.deb Are we to assume negation as failure here or are there already packages available for feisty and gutsy somewhere? Chris Menzel
Math font error on Lyx - Windows
Hi, I am using lyx 1.5.2 for windows XP, MiKTeX 2.5. When using pdflatex to produce output, everything works great until I enter any math characters, when I get the following LaTeX error Font \csname\endcsname=psyr at 10.0pt not loadable: Metric (TFM) file not found Can anybody help me solve this problem Thanks, Andrew
Re: Incoming 1.5.3 binaries for debian/ubuntu distributions
On Thu, Jan 17, 2008 at 04:24:39PM +, Sam Lewis wrote: > Sven Hoexter <[EMAIL PROTECTED]> writes: Hi, > > Sam please don't take it as an offense but I'd highly recommend to not > > use those checkinstall packages for Debian/etch. The same reasoning > > apply for Ubuntu so you might want to read on as an Ubuntu user > > aswell. > To clarify these are not official packages, but made available by me > for other LyX users, on debian-based distros, who don't want to wait > until official releases included these versions. There will never be new versions in a stable release of Debian or Ubuntu. (Beside maybe Firefox/Iceweasel but that's based on upstreams security update policy and a different matter.) > I've provided packages for several years and there have been no > complaints. They are built on non-modified releases of etch and dapper > and by reading the README file (that are also uploaded) one gets a good > idea about build dependencies. No complains can mean to things. Nobody used the package or nobody noticed the problem. You might guess it but there are control fields for build dependencies so that you don't have to write them down in a second file. > If 1.5.3 is is already available on backports.org that's great, and my > packages are not be needed then. If not, than responsible users might > choose to uses these. It's not avaible on backports or but there is a backport avaible. > > One backdraw is that you're forced to migrate to texlive from tetex > > if you're still using tetex. This will happen with lenny anyway but > > it will force you to download a few hundred MiB of texlive packages > > along with the new LyX and boost packages. > > There are no tex-distro decencies set on my packages, one can uses > whatever one likes. Indeed, I thought, it was in the very spirit of > LyX, that some users provide there binaries for other users without > predefining every interacting software. > ./configure --with-qt-dir=/usr/share/qt4 --enable-optimization=-O3 > --prefix=/usr/local At least you choose /usr/local which will prevent worst some breakage. To be clear there are two sides of the story to consider: a) The social/trust problem There's someone providing binarys build on an unknown system with under unknown conditions and you've to install those binarys as superuser. So someone I don't know and by definition don't trust will do things with superuser rights. That can't be good. You don't need to have to be evil but you or your tool might do something bad. I vaguely remember that someone last year noticed that people included his repository of 3rd party Ubuntu packages in generic sources.list files passed around in forums/mailinglists. So he decided to make the naiv people using those lists aware of the problem and provided a wallpaper upgrade for the user desktop with a big warning. It made some press at that time but sadly I don't remember the name of the guy but I guess with some proper search terms you should be able to find it. The problem is very similar here. I would be surprised if Juergen unpacked the provided packages to check at least the maintainer scripts for some evil code. That still would not proofe that you did not modify the LyX source. b) Technical problems ba) You're breaking the upgrade path. Let's say under bad conditions the next Debian stable release will be delivered with LyX 1.5.3 packages. What do you guess happens on a system with etch running your packages on the upgrade? Bingo nothing for the LyX package because it has the same version number. So there will be users with an untrusted package compiled with some completly different libs not matching there current system. bb) Maintainer scripts have a reason If you take a look at the diff.gz of the Debian packages you'll find out that there are maintainer scripts for post/pre install execution. That these scripts exists has a reason and the reason is not that the package maintainers like to add some strange scripts to make their packages look cool. For example somebody doing QA work recently noticed that we've left an /etc/lyxrc file on the system with the 1.4.x->1.5.x upgrade which should not happen. So we're now cleaning up behind us with a maintainer script which is of course bound to special versions. You'll break if you install your current package an try to upgrade it at a later point to a Debian version again. In this case it's only an unused old file but it could of course be anything more important. Another example might be the execution of texhash to integrate the beamer files correctly. bc) Dependencies don't exist for fun. Dependencies are very near at the heart of any kind of package management system. If you provide a package without proper dependencies you're messing in a very sensitive area which is prone to cause subtle problems. Libs change from time to time and you don't even notice that and you're package manger can't even warn you. bd) i386? And where is the rest? Even De
Re: Math font error on Lyx - Windows
Andrew Barr wrote: > > I am using lyx 1.5.2 for windows XP, MiKTeX 2.5. > > When using pdflatex to produce output, everything works great until I > enter > any math characters, when I get the following LaTeX error > > Font \csname\endcsname=psyr at 10.0pt not loadable: Metric (TFM) file not > found > I can't reproduce this problem with a standard document class, and I wouldn't know how to help if I could. However, I suspect it will help if you let us know which document class you're working with and which fonts you've specified in the Documents -> Settings. - David Hewitt Virginia Institute of Marine Science http://www.vims.edu/fish/students/dhewitt/ -- View this message in context: http://www.nabble.com/Math-font-error-on-Lyx---Windows-tp14927537p14932995.html Sent from the LyX - Users mailing list archive at Nabble.com.
Re: Incoming 1.5.3 binaries for debian/ubuntu distributions
Sven Hoexter <[EMAIL PROTECTED]> writes: > To be clear there are two sides of the story to consider: Thank you for your comprehensive account, trying to shed light on the situation! > a) The social/trust problem > There's someone providing binarys build on an unknown system with under > unknown conditions and you've to install those binarys as superuser. > So someone I don't know and by definition don't trust will do things > with superuser rights. That can't be good. You don't need to have to > be evil but you or your tool might do something bad. Indeed (as I had mentioned on the development list earlier today) any installation soever --from an "unknown"-- presents a serious security issues. To say it again: `At present all that can be "known", is that someone from a specific email address sends an announcement to the LyX list about a new binary being available. This indeed is not very safe, yet with each day that passes (without someone complaining on the list about the binary) and with every new binary announced--from one an the same email address--it becomes more and more "safe".' In addition, the more time passes, the more like it might be that someone will notice errors, malicious or not. What solution could you think of? Does the development team use key? > b) Technical problems I guess this is a specific debian issue you're raising and might differ at each distro (my apologies to for the possibly off-list-topic discussion here). > ba) You're breaking the upgrade path. > Let's say under bad conditions the next Debian stable release will be > delivered with LyX 1.5.3 packages. What do you guess happens on a > system with etch running your packages on the upgrade? Bingo nothing > for the LyX package because it has the same version number. > So there will be users with an untrusted package compiled with some > completly different libs not matching there current system. True, if you are using checkinstall binaries and (in the unlikely event of) your stable debian release upgrading to this specific lyx release, libraries might most probably not match. All you need to do is to reinstall, through the comfort of checkinstall the offending lyx package. sudo dpkg -r lyx > bb) Maintainer scripts have a reason > If you take a look at the diff.gz of the Debian packages you'll find > out that there are maintainer scripts for post/pre install execution. > That these scripts exists has a reason and the reason is not that > the package maintainers like to add some strange scripts to make > their packages look cool. > > For example somebody doing QA work recently noticed that we've left > an /etc/lyxrc file on the system with the 1.4.x->1.5.x upgrade which > should not happen. So we're now cleaning up behind us with a maintainer > script which is of course bound to special versions. You'll break if > you install your current package an try to upgrade it at a later point > to a Debian version again. In this case it's only an unused old file > but it could of course be anything more important. So how about a recommendation that users when installing a checkinstall binary should uses the following command line: sudo dpkg -r lyx && sudo dpkg -i lyx_1.5.3-1_i386_etch.deb && sudo apt-get -f install > bc) Dependencies don't exist for fun. See above. > bd) i386? And where is the rest? Yep that would be good, but to make it clear, this is an instrumental move. I'm not a developer or maintainer; I am a social scientist, who uses LyX on a daily basis on computers that happen to be i386. For the benefit of others, I am providing my own compiled binaries, for others who don't have the knowledge or the resources to compile the source themselves. > At least I don't see any benefit in the checkinstall crap Checkinstall is a very safe way to install your own complied source, for the very reason that you can remove it in a simple and safe way, which is important as you rightly pointed out. If you choose to install someone else binary relates back to the point of trust. > I might be one of the rare cases of users who used one installation for > seven years with several hardware changes. If you'd like to reinstall > a clean system with every stable release of your distribution of choice > go ahead and use broken packages. Impressive -- this deserves applause! Don't get my wrong, your concerns are valid, but there are many pragmatic and practical reason as to why people compile their own software rather than waiting for a backport or using a rather old version of it. Perhaps this has shed more light on the issues of user-built packages, in general and debian in specific. What do other people think? Cheers, Sam
Re: LyX Qt under Gnome environment
Le jeudi 17 janvier 2008 08:20:09 +0100 Guido Milanese <[EMAIL PROTECTED]> écrivait : Questions: > (1) is compilation on Ubuntu difficult? I thinks that compiling and > installing manually should avoid the problem I mentioned; > (2) if (1) is not practical, can anyone suggest all the symlink that > I should set up to persuade Synaptic that I have already a TeX system > running? 1. Compilation would probably be your best choice. The only thing is to have all the necessary packages already installed. These packages have -dev in their name. a) first, desinstall your old LyX: sudo apt-get remove lyx lyx-common b) download lyx_1.5.3 sources and decompress in a temporary repertory tar xvfj /home/yourname/tmp/lyx-1.5.3.tar.bz2 c) cd tmp/lyx-1.5.3 d) you may read the install instructions: less INSTALL (q to quit) e) be sure you have everything to compile, this means for LyX-Qt: sudo apt-get install libqt4-core libqt4-dev qt4-qtconfig python-qt4 python-qt4-dev build-essential I may forget other packages... f) ./configure --prefix=/usr don't forget the dot before /configure, the --prefix=/usr switch is for an installation in the same directory as it was in Ubuntu 7.10 g) if everything is OK, you will see the message inviting you to continue by typing make otherwise, an error message will probably cite the name of the missing library, install it with sudo apt-get install thename AND press Tab for suggestion and auto-completion, take the -dev package h) a compilation is OK when it ends with these words (or similar): Leaving xyz directory Nothing to be done for all. i) Finally you have 2 choices for installation: 1- sudo make install and hop it goes! You will have to add LyX manually in your menu. 2- sudo checkinstall (but you have to install before checkinstall by typing sudo apt-get install checkinstall) checkinstall will create a .deb package of LyX 1.5.3. This wy it is very easy to uninstall or install on a similar system. I understand that a checkinstall package is not a .deb with the rules of art, but for your own use, it is usefull and easy. You can safely erase all the files in /tmp/lyx... except the lyx-1.5.3 deb file that you just create. If you never compile LyX before, be patient, it may take 10 to 30 minutes depending of your PC. Good luck! Raymond Édité et transmis avec des logiciels libres sous Linux !
Re: Math font error on Lyx - Windows
David, Sorry I didn't include that information. I was using Times Roman font. I changed the font settings to default, and all the math comes through fine. So...I guess that problem is solved for the moment. Sorry for the dumb question. Thanks
Re: generic X copy-and-paste not working
On 17.01.08, Jeremy C. Reed wrote: > Normally, I can highlight text in a terminal and paste it with a > middle-click. In LyX, usually I can get to it with Edit -> Paste Special. > (I can copy-and-paste fine in my xterms.) > In my LyX, the Paste Special choices are shaded out and not clickable. > This is LyX 1.5.2 on NetBSD. I am not running any clipboard utility. > Any ideas why I can't paste into LyX? I did a test on my LyX 1.5.3 on Debian/testing++ with XFCE4 and xfce4-clipman and got very strange results: A newly opened LyX (first time after starting the Computer) with a new buffer did not accept any mouse-pasting (middle click) from xterms or xjed. (Whether with a simple middel click or via Edit>Paste did not matter.) Just typing some text in the LyX window did not change this behaviour. After marking some text (with mouse) and Ctrl-C, I could paste this text with a middle-mouse click. Now also pasting text from other applications works fine. Closing LyX and opening a new one: The second time pasting works from the start. Any clues? Guenter
