Re: Finally figuring out some ob-sqlite stuff -- for worg?
Eric Abrahamsen writes: > I was confused in part because the "where exists (select *..." looks > like its main purpose is to return rows. Indeed that's the purpose: Restrict the set of rows upon which update acts on. Here I tried to reformat the statement a bit in order to emphasize its structure: #+begin_src sql UPDATE bookreview SET rating = (select rating from updates where bookreview.id = updates.id) WHERE EXISTS (select * from updates where updates.id = bookreview.id); #+end_src The subselect of the "SET rating" part is a correlated subquery. So if you imagine UPDATE as a kind of loop over the table, the subquery of the SET part is executed once for every row UPDATE acts on (maybe the SQL execution engine optimizes this in some kind, but the mental model here is: run the subquery for every row we visit on our journey throught the table). Only the WHERE EXISTS clause belonging directly to the UPDATE statement will reduce the set of rows to act on. > Will the select subquery actually restrict the values that are > available for updating/comparison in the update statement? No. > Or does the "exists" mean the subquery is treated as a plain yes/no > boolean, and the update still has access to anything it likes? We > could write "where exists (select " to the same effect? Yes. The SELECT clause of an EXISTS subquery (as in the above example) is rather meaningless. So somethimes you see constructs like "where exists (select 1 from ...)". Some SQL engines are not very clever and execute the subquery of such an EXISTS clause unchanged - meaning that way too much data is fetched for the intermediate result (unnecessary IO and maybe polluting caches). Thus the "select 1" as a workaround for those unclever engines. But current engines should have no problems with optimizing these EXISTS subqueries and in that case it does not matter how the select clause looks like - it will be ignored. > In essence, the "where exists" is acting as an "inner join"... Yes, effectively we are simulating an inner join at this point. Sadly, many SQL engines are not able to update rows of join constructs (or at least have quite severe constraints in these cases). Thus we need to build these kinds of workarounds to change data in more complex cases. SQL is quite a capable language, but it has also has some rough edges. :) -- Until the next mail..., Stefan.
Re: Using Org and eev together - problem with source blocks
On 2019-11-10 at 02:54 +01, Eduardo Ochs wrote... > #+BEGIN_SRC python > def square (x): > return x*x > > print(square(5)) > #+END_SRC > > [...] when I run the Python block with C-c C-c I always get a results > block like this (without the indentation): > > #+RESULTS: > : None > > What am I doing wrong? I expected an output of "25"... =( Adding ":output results" makes this work for me, but I'm not using emacs24. -k.
Re: Bug: Cursor Disapears in Org-Src Blocks in Indent Mode [9.2.6 (release_9.2.6-559-ga01a8f @ /Users/djm/.emacs.d/straight/build/org/)]
On Friday, 8 Nov 2019 at 10:41, Dylan McDowell wrote: > Expected Behavior: My cursor is always visible throughout my entire > org-document > > Actual Behavior: When moving through org-src blocks, my cursor is > visible until I move it to the end of the line. Then my cursor disapears > and only shows up when the cursor is placed in the middle of the line. I imagine this is a bug in Emacs, not org, one that people are currently trying to track down. See the emacs developers mailing list. The problem has to do with faces that have the :extend attribute set and especially those with a different background. On the developers list, they are looking for an easily reproducible example starting from emacs -Q, by the way... -- Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78
Re: customized link pointing at a src block
You want the equivalent of the LaTeX exporter's ,[ C-h v org-latex-prefer-user-labels RET ] | org-latex-prefer-user-labels is a variable defined in ‘ox-latex.el’. | Its value is t | Original value was nil | | You can customize this variable. | | | This variable was introduced, or its default value was changed, in | version 26.1 of Emacs. | | Documentation: | Use user-provided labels instead of internal ones when non-nil. | | [...] | | For headlines that do not define the CUSTOM_ID property or | elements without a NAME, Org will continue to use its default | labeling scheme to generate labels and resolve links into proper | references. ` I don't think the HTML exporter has anything similar but it should be possible to implement... -- Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78
Truncate lines option on file startup
Hi, Thought it would be handy to be able to do this: #+STARTUP: truncate and #+STARTUP: notruncate Modifying org-startup-options manually wouldn't work as it describes how to change a value of a variable or push onto a list, but no syntax for function calls and for this to work toggle-truncate-lines is to be envoked. I know about org-startup-truncated, but it's not file-by-file precision. PS if this turns out to be hairy, I can use .dir-locals.el, but the feature would still be a nice-to-have. Regards, Dmitrii
Re: Truncate lines option on file startup
On Sunday, 10 Nov 2019 at 18:12, Dmitrii Korobeinikov wrote: > PS if this turns out to be hairy, I can use .dir-locals.el, but the feature > would still be a nice-to-have. You could use file local variables for this, e.g. # Local Variables: # truncate-lines: t # End: at the end of your org file or # -*- truncate-lines: t; -*- as the first line of your file. This is not org specific so I guess there is no real justification for an org variable for this feature. -- Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78
[O bug] table debugging does not preserve window configuration
Hello all,
If I turn debugging on for table updates (C-c {), when the debugging is
finished, the original window configuration is not remembered.
Should be simple to fix, but possibly beyond my emacs-lisp-fu.
Thanks,
eric
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78
Re: Using Org and eev together - problem with source blocks
Changing the Python source block to #+BEGIN_SRC python :output results def square (x): return x*x print(square(5)) #+END_SRC didn't change anything here, neither with emacs24 nor with git emacs, and I grepped (recursively) for ":output" in the directory where I cloned https://code.orgmode.org/bzg/org-mode.git and only found references to ":output-dir" - except for a single occurrence of ":output" in contrib/lisp/ob-sclang.el... Are you sure that you wrote it correctly? Cheers, E. =) http://angg.twu.net/#eev On Sun, 10 Nov 2019 at 08:39, Ken Mankoff wrote: > > On 2019-11-10 at 02:54 +01, Eduardo Ochs wrote... > > #+BEGIN_SRC python > > def square (x): > > return x*x > > > > print(square(5)) > > #+END_SRC > > > > [...] when I run the Python block with C-c C-c I always get a results > > block like this (without the indentation): > > > > #+RESULTS: > > : None > > > > What am I doing wrong? I expected an output of "25"... =( > > Adding ":output results" makes this work for me, but I'm not using emacs24. > > -k. >
Re: Using Org and eev together - problem with source blocks
On 2019-11-10 at 15:36 +01, Eduardo Ochs wrote... > Changing the Python source block to > > #+BEGIN_SRC python :output results > > Are you sure that you wrote it correctly? I'm pretty sure I did not. Try ":results output" -k.
Re: Finally figuring out some ob-sqlite stuff -- for worg?
Stefan Nobis writes: > Eric Abrahamsen writes: > >> I was confused in part because the "where exists (select *..." looks >> like its main purpose is to return rows. > > Indeed that's the purpose: Restrict the set of rows upon which update > acts on. Here I tried to reformat the statement a bit in order to > emphasize its structure: Right -- I should have phrased that as "looks like its main purpose is to return data from rows", which as you clarify below, isn't its main purpose. > #+begin_src sql > UPDATE bookreview > SET rating = (select rating from updates > where bookreview.id = updates.id) > WHERE EXISTS (select * from updates > where updates.id = bookreview.id); > #+end_src > > The subselect of the "SET rating" part is a correlated subquery. So if > you imagine UPDATE as a kind of loop over the table, the subquery of > the SET part is executed once for every row UPDATE acts on (maybe the > SQL execution engine optimizes this in some kind, but the mental model > here is: run the subquery for every row we visit on our journey > throught the table). > > Only the WHERE EXISTS clause belonging directly to the UPDATE > statement will reduce the set of rows to act on. > >> Will the select subquery actually restrict the values that are >> available for updating/comparison in the update statement? > > No. > >> Or does the "exists" mean the subquery is treated as a plain yes/no >> boolean, and the update still has access to anything it likes? We >> could write "where exists (select " to the same effect? > > Yes. The SELECT clause of an EXISTS subquery (as in the above example) > is rather meaningless. So somethimes you see constructs like "where > exists (select 1 from ...)". Some SQL engines are not very clever and > execute the subquery of such an EXISTS clause unchanged - meaning that > way too much data is fetched for the intermediate result (unnecessary > IO and maybe polluting caches). Thus the "select 1" as a workaround > for those unclever engines. But current engines should have no > problems with optimizing these EXISTS subqueries and in that case it > does not matter how the select clause looks like - it will be ignored. > >> In essence, the "where exists" is acting as an "inner join"... > > Yes, effectively we are simulating an inner join at this point. Sadly, > many SQL engines are not able to update rows of join constructs (or at > least have quite severe constraints in these cases). Thus we need to > build these kinds of workarounds to change data in more complex cases. > > SQL is quite a capable language, but it has also has some rough edges. > :) Really interesting! Thanks again for the in-depth explanation
Re: Finally figuring out some ob-sqlite stuff -- for worg?
Stefan Nobis writes: > Eric Abrahamsen writes: > >> I was confused in part because the "where exists (select *..." looks >> like its main purpose is to return rows. > > Indeed that's the purpose: Restrict the set of rows upon which update > acts on. Here I tried to reformat the statement a bit in order to > emphasize its structure: Right -- I should have phrased that as "looks like its main purpose is to return data from rows", which as you clarify below, isn't its main purpose. > #+begin_src sql > UPDATE bookreview > SET rating = (select rating from updates > where bookreview.id = updates.id) > WHERE EXISTS (select * from updates > where updates.id = bookreview.id); > #+end_src > > The subselect of the "SET rating" part is a correlated subquery. So if > you imagine UPDATE as a kind of loop over the table, the subquery of > the SET part is executed once for every row UPDATE acts on (maybe the > SQL execution engine optimizes this in some kind, but the mental model > here is: run the subquery for every row we visit on our journey > throught the table). > > Only the WHERE EXISTS clause belonging directly to the UPDATE > statement will reduce the set of rows to act on. > >> Will the select subquery actually restrict the values that are >> available for updating/comparison in the update statement? > > No. > >> Or does the "exists" mean the subquery is treated as a plain yes/no >> boolean, and the update still has access to anything it likes? We >> could write "where exists (select " to the same effect? > > Yes. The SELECT clause of an EXISTS subquery (as in the above example) > is rather meaningless. So somethimes you see constructs like "where > exists (select 1 from ...)". Some SQL engines are not very clever and > execute the subquery of such an EXISTS clause unchanged - meaning that > way too much data is fetched for the intermediate result (unnecessary > IO and maybe polluting caches). Thus the "select 1" as a workaround > for those unclever engines. But current engines should have no > problems with optimizing these EXISTS subqueries and in that case it > does not matter how the select clause looks like - it will be ignored. > >> In essence, the "where exists" is acting as an "inner join"... > > Yes, effectively we are simulating an inner join at this point. Sadly, > many SQL engines are not able to update rows of join constructs (or at > least have quite severe constraints in these cases). Thus we need to > build these kinds of workarounds to change data in more complex cases. > > SQL is quite a capable language, but it has also has some rough edges. > :) Really interesting! Thanks again for the in-depth explanation.
Publish to PDF on Linux: An impossible task?
After using org-mode for 10 years, I run for the doorway when I even think about trying to convert an org-mode file to PDF. *** I quiver when I see errors such as: warning: kpathsea: configuration file texmf.cnf not found in these directories: /usr/bin:/usr/bin/share/texmf-local/web2c:/usr/bin/share/texmf-dist/web2c:/usr/bin/share/texmf/web2c:/usr/bin/texmf-local/web2c:/usr/bin/texmf-dist/web2c:/usr/bin/texmf/web2c:/usr:/usr/share/texmf-local/web2c:/usr/share/texmf-dist/web2c:/usr/share/texmf/web2c:/usr/texmf-local/web2c:/usr/texmf-dist/web2c:/usr/texmf/web2c://texmf-local/web2c:/://share/texmf-local/web2c://share/texmf-dist/web2c://share/texmf/web2c://texmf-local/web2c://texmf-dist/web2c://texmf/web2c. This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch Linux) (preloaded format=pdflatex) kpathsea: Running mktexfmt pdflatex.fmt mktexfmt: No such file or directory I can't find the format file `pdflatex.fmt'! *** I run for cover when I read documentation such as: https://orgmode.org/manual/LaTeX-Export.html#LaTeX-Export I think people who have been using LaTex and related tools for a long time have no issue with this (seemingly) insurmountable feat. However, I am not familiar with such a myriad of tools and I'm simply looking for the "easiest" way to convert/export an org mode file to PDF on Linux. Can anyone point me to some tutorials? I'm sorry if I miss something obvious. Thanks, --Nate
Re: Publish to PDF on Linux: An impossible task?
On 2019-11-11, at 01:00, Nathan Neff wrote: > After using org-mode for 10 years, I run for the doorway when > I even think about trying to convert an org-mode file to PDF. > > *** I quiver when I see errors such as: > > warning: kpathsea: configuration file texmf.cnf not found in these > directories: > /usr/bin:/usr/bin/share/texmf-local/web2c:/usr/bin/share/texmf-dist/web2c:/usr/bin/share/texmf/web2c:/usr/bin/texmf-local/web2c:/usr/bin/texmf-dist/web2c:/usr/bin/texmf/web2c:/usr:/usr/share/texmf-local/web2c:/usr/share/texmf-dist/web2c:/usr/share/texmf/web2c:/usr/texmf-local/web2c:/usr/texmf-dist/web2c:/usr/texmf/web2c://texmf-local/web2c:/://share/texmf-local/web2c://share/texmf-dist/web2c://share/texmf/web2c://texmf-local/web2c://texmf-dist/web2c://texmf/web2c. > This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch Linux) > (preloaded format=pdflatex) > > kpathsea: Running mktexfmt pdflatex.fmt > mktexfmt: No such file or directory > I can't find the format file `pdflatex.fmt'! This looks like a broken installation of TeXlive to me, although I'm definitely not an expert on kpathsea or mktexfmt. Another conjecture is that Arch's TeXlive needs some environment variable which is only set for interactive sessions. (This would be strange.) This is a very long shot, but what would happen if you compiled a short, hello-world-type LaTeX document in the console? Would Org-mode export work after this? Also, what does this: ~set | grep ^TEX~ say in a console? And in M-x shell? For my way, see below. > *** I run for cover when I read documentation such as: > > https://orgmode.org/manual/LaTeX-Export.html#LaTeX-Export > > I think people who have been using LaTex and related tools for a long time > have > no issue with this (seemingly) insurmountable feat. However, I am not > familiar with > such a myriad of tools and I'm simply looking for the "easiest" way to > convert/export an org > mode file to PDF on Linux. > > Can anyone point me to some tutorials? I'm sorry if I miss something > obvious. I've been using pdf export many times without any problems. My secret is using TeXlive from the TeXlive distribution, not from my GNU/Linux distribution. (Last time I checked, Ubuntu's TeXlive was hopelessly out of date. Even though I've been using Arch for a few years now, I still install TeXlive from https://tug.org/texlive/ . One big advantage of that is that the installer lets me install only stuff I need, and if I later decide that I need something more, I can install even an individual class/package/font/whatever. Another plus is that I can easily install a few versions of TeXlive and e.g. develop my classes with the latest one, but test them also on an older version.) Also, the installer lets me put TeXlive in my home directory, so it can be installed even without root privileges. Hth, -- Marcin Borkowski http://mbork.pl
Re: Publish to PDF on Linux: An impossible task?
On Sun, Nov 10, 2019 at 6:01 PM Nathan Neff wrote: > > After using org-mode for 10 years, I run for the doorway when > I even think about trying to convert an org-mode file to PDF. > > *** I quiver when I see errors such as: > > warning: kpathsea: configuration file texmf.cnf not found in these > directories: > /usr/bin:/usr/bin/share/texmf-local/web2c:/usr/bin/share/texmf-dist/web2c:/usr/bin/share/texmf/web2c:/usr/bin/texmf-local/web2c:/usr/bin/texmf-dist/web2c:/usr/bin/texmf/web2c:/usr:/usr/share/texmf-local/web2c:/usr/share/texmf-dist/web2c:/usr/share/texmf/web2c:/usr/texmf-local/web2c:/usr/texmf-dist/web2c:/usr/texmf/web2c://texmf-local/web2c:/://share/texmf-local/web2c://share/texmf-dist/web2c://share/texmf/web2c://texmf-local/web2c://texmf-dist/web2c://texmf/web2c. > This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch Linux) > (preloaded format=pdflatex) > > kpathsea: Running mktexfmt pdflatex.fmt > mktexfmt: No such file or directory > I can't find the format file `pdflatex.fmt'! These look like latex errors to me, nothing to do with Org. Guessing you used the arch package? I'm on arch myself, but after getting bitten by package mismatches and things being hopelessly broken, I switched to just using texlive directly: - https://www.tug.org/texlive/ It's not that bad. There's even a quick guide to walk you through the tl-install script. If you'd rather troubleshoot what you have going on now, here's some places to start: - you're missing files... figure out which package is supposed to provide them and install it - check your paths - google the error and see what you find > *** I run for cover when I read documentation such as: > > https://orgmode.org/manual/LaTeX-Export.html#LaTeX-Export > > I think people who have been using LaTex and related tools for a long time > have > no issue with this (seemingly) insurmountable feat. However, I am not > familiar with > such a myriad of tools and I'm simply looking for the "easiest" way to > convert/export an org > mode file to PDF on Linux. I would save this for last. For now, just take your document and export to the .tex file (don't compile). Then go to a command line and do: $ pdflatex ./file.tex and see what happens. Until you can do that manually, nothing from the Org side will help you. In fact, Org just assumes that this stuff exists, spits out the right .tex file based on your markdown, and leverages the existing latex system utilities to process it. This will end up being that you don't have a functioning latex setup on your system, and thus Org can't work its magic. John > > Can anyone point me to some tutorials? I'm sorry if I miss something obvious. > > Thanks, > --Nate
Re: Publish to PDF on Linux: An impossible task?
On 2019-11-11, at 01:25, John Hendy wrote: > On Sun, Nov 10, 2019 at 6:01 PM Nathan Neff wrote: >> >> After using org-mode for 10 years, I run for the doorway when >> I even think about trying to convert an org-mode file to PDF. >> >> *** I quiver when I see errors such as: >> >> warning: kpathsea: configuration file texmf.cnf not found in these >> directories: >> /usr/bin:/usr/bin/share/texmf-local/web2c:/usr/bin/share/texmf-dist/web2c:/usr/bin/share/texmf/web2c:/usr/bin/texmf-local/web2c:/usr/bin/texmf-dist/web2c:/usr/bin/texmf/web2c:/usr:/usr/share/texmf-local/web2c:/usr/share/texmf-dist/web2c:/usr/share/texmf/web2c:/usr/texmf-local/web2c:/usr/texmf-dist/web2c:/usr/texmf/web2c://texmf-local/web2c:/://share/texmf-local/web2c://share/texmf-dist/web2c://share/texmf/web2c://texmf-local/web2c://texmf-dist/web2c://texmf/web2c. >> This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch Linux) >> (preloaded format=pdflatex) >> >> kpathsea: Running mktexfmt pdflatex.fmt >> mktexfmt: No such file or directory >> I can't find the format file `pdflatex.fmt'! > > These look like latex errors to me, nothing to do with Org. Guessing These are not LaTeX errors, they are lower-level ones. > you used the arch package? I'm on arch myself, but after getting > bitten by package mismatches and things being hopelessly broken, I > switched to just using texlive directly: > - https://www.tug.org/texlive/ > > It's not that bad. There's even a quick guide to walk you through the > tl-install script. If you'd rather troubleshoot what you have going on > now, here's some places to start: > - you're missing files... figure out which package is supposed to > provide them and install it He misses LaTeX format file itself, and apparently mktexfmt (which should create it) cannot be found. This seems more serious than what you write. > - check your paths Agreed, but this may be quite subtle... Best, -- Marcin Borkowski http://mbork.pl
Re: Publish to PDF on Linux: An impossible task?
On Sun, Nov 10, 2019 at 6:41 PM Marcin Borkowski wrote: > > > On 2019-11-11, at 01:25, John Hendy wrote: > > > On Sun, Nov 10, 2019 at 6:01 PM Nathan Neff wrote: > >> > >> After using org-mode for 10 years, I run for the doorway when > >> I even think about trying to convert an org-mode file to PDF. > >> > >> *** I quiver when I see errors such as: > >> > >> warning: kpathsea: configuration file texmf.cnf not found in these > >> directories: > >> /usr/bin:/usr/bin/share/texmf-local/web2c:/usr/bin/share/texmf-dist/web2c:/usr/bin/share/texmf/web2c:/usr/bin/texmf-local/web2c:/usr/bin/texmf-dist/web2c:/usr/bin/texmf/web2c:/usr:/usr/share/texmf-local/web2c:/usr/share/texmf-dist/web2c:/usr/share/texmf/web2c:/usr/texmf-local/web2c:/usr/texmf-dist/web2c:/usr/texmf/web2c://texmf-local/web2c:/://share/texmf-local/web2c://share/texmf-dist/web2c://share/texmf/web2c://texmf-local/web2c://texmf-dist/web2c://texmf/web2c. > >> This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch Linux) > >> (preloaded format=pdflatex) > >> > >> kpathsea: Running mktexfmt pdflatex.fmt > >> mktexfmt: No such file or directory > >> I can't find the format file `pdflatex.fmt'! > > > > These look like latex errors to me, nothing to do with Org. Guessing > > These are not LaTeX errors, they are lower-level ones. By "LaTeX" I mean "that which is necessary to have a functioning latex system." If by lower-level you mean the ecosystem itself vs. compiling errors, completely agree. Clearly some core components are missing. For example, the texmf.cnf file is provided by the arch package texlive-core (assuming a package was used), so that's potentially not even installed. - https://www.archlinux.org/packages/extra/any/texlive-core/ > > you used the arch package? I'm on arch myself, but after getting > > bitten by package mismatches and things being hopelessly broken, I > > switched to just using texlive directly: > > - https://www.tug.org/texlive/ > > > > It's not that bad. There's even a quick guide to walk you through the > > tl-install script. If you'd rather troubleshoot what you have going on > > now, here's some places to start: > > - you're missing files... figure out which package is supposed to > > provide them and install it > > He misses LaTeX format file itself, and apparently mktexfmt (which > should create it) cannot be found. This seems more serious than what > you write. I would divide "serious" into "major but simple" and "complicated." In easily 90% of cases with error output like this, it's going to be a missing package, not some intricate system glitch that requires troubleshooting. Indeed, my guess is exactly that: there are "serious" errors because nothing resembling a functioning latex system exists. The root cause is probably very simple. > > - check your paths > > Agreed, but this may be quite subtle... Again, I suspect much simpler. When using texlive directly, for example, one has to set paths correctly. This If it's looking in system paths vs. a user path (e.g. I install to ~/.texlive, not /usr) and this was not set via .bashrc, that's what I mean one should check. This presumes the expected packages are installed at all. I would start with simply: $ pacman -Q |grep tex and $ which pdflatex John > > Best, > > -- > Marcin Borkowski > http://mbork.pl
Re: Publish to PDF on Linux: An impossible task?
This looks like an incomplete textLive install to me. On many distributions, texlive is broken up into a number of smaller packages. You need to ensure you have installed the texlive latex packages. I would follow the advice of others and just use the package from the texlive site. On Mon, 11 Nov 2019 at 11:41, Marcin Borkowski wrote: > > On 2019-11-11, at 01:25, John Hendy wrote: > > > On Sun, Nov 10, 2019 at 6:01 PM Nathan Neff > wrote: > >> > >> After using org-mode for 10 years, I run for the doorway when > >> I even think about trying to convert an org-mode file to PDF. > >> > >> *** I quiver when I see errors such as: > >> > >> warning: kpathsea: configuration file texmf.cnf not found in these > directories: > /usr/bin:/usr/bin/share/texmf-local/web2c:/usr/bin/share/texmf-dist/web2c:/usr/bin/share/texmf/web2c:/usr/bin/texmf-local/web2c:/usr/bin/texmf-dist/web2c:/usr/bin/texmf/web2c:/usr:/usr/share/texmf-local/web2c:/usr/share/texmf-dist/web2c:/usr/share/texmf/web2c:/usr/texmf-local/web2c:/usr/texmf-dist/web2c:/usr/texmf/web2c://texmf-local/web2c:/://share/texmf-local/web2c://share/texmf-dist/web2c://share/texmf/web2c://texmf-local/web2c://texmf-dist/web2c://texmf/web2c. > >> This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch > Linux) (preloaded format=pdflatex) > >> > >> kpathsea: Running mktexfmt pdflatex.fmt > >> mktexfmt: No such file or directory > >> I can't find the format file `pdflatex.fmt'! > > > > These look like latex errors to me, nothing to do with Org. Guessing > > These are not LaTeX errors, they are lower-level ones. > > > you used the arch package? I'm on arch myself, but after getting > > bitten by package mismatches and things being hopelessly broken, I > > switched to just using texlive directly: > > - https://www.tug.org/texlive/ > > > > It's not that bad. There's even a quick guide to walk you through the > > tl-install script. If you'd rather troubleshoot what you have going on > > now, here's some places to start: > > - you're missing files... figure out which package is supposed to > > provide them and install it > > He misses LaTeX format file itself, and apparently mktexfmt (which > should create it) cannot be found. This seems more serious than what > you write. > > > - check your paths > > Agreed, but this may be quite subtle... > > Best, > > -- > Marcin Borkowski > http://mbork.pl > > -- regards, Tim -- Tim Cross
Re: Publish to PDF on Linux: An impossible task?
there is also pandoc, if you know something that you can export to that pandoc can reasonably convert. like, who knows, html or something. this might be useful if you are in a hurry or you don't want to install a non-distribution package or whatever. On 11/10/19, Tim Cross wrote: > This looks like an incomplete textLive install to me. > > On many distributions, texlive is broken up into a number of smaller > packages. You need to ensure you have installed the texlive latex packages. > > I would follow the advice of others and just use the package from the > texlive site. > > > > On Mon, 11 Nov 2019 at 11:41, Marcin Borkowski wrote: > >> >> On 2019-11-11, at 01:25, John Hendy wrote: >> >> > On Sun, Nov 10, 2019 at 6:01 PM Nathan Neff >> wrote: >> >> >> >> After using org-mode for 10 years, I run for the doorway when >> >> I even think about trying to convert an org-mode file to PDF. >> >> >> >> *** I quiver when I see errors such as: >> >> >> >> warning: kpathsea: configuration file texmf.cnf not found in these >> directories: >> /usr/bin:/usr/bin/share/texmf-local/web2c:/usr/bin/share/texmf-dist/web2c:/usr/bin/share/texmf/web2c:/usr/bin/texmf-local/web2c:/usr/bin/texmf-dist/web2c:/usr/bin/texmf/web2c:/usr:/usr/share/texmf-local/web2c:/usr/share/texmf-dist/web2c:/usr/share/texmf/web2c:/usr/texmf-local/web2c:/usr/texmf-dist/web2c:/usr/texmf/web2c://texmf-local/web2c:/://share/texmf-local/web2c://share/texmf-dist/web2c://share/texmf/web2c://texmf-local/web2c://texmf-dist/web2c://texmf/web2c. >> >> This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch >> Linux) (preloaded format=pdflatex) >> >> >> >> kpathsea: Running mktexfmt pdflatex.fmt >> >> mktexfmt: No such file or directory >> >> I can't find the format file `pdflatex.fmt'! >> > >> > These look like latex errors to me, nothing to do with Org. Guessing >> >> These are not LaTeX errors, they are lower-level ones. >> >> > you used the arch package? I'm on arch myself, but after getting >> > bitten by package mismatches and things being hopelessly broken, I >> > switched to just using texlive directly: >> > - https://www.tug.org/texlive/ >> > >> > It's not that bad. There's even a quick guide to walk you through the >> > tl-install script. If you'd rather troubleshoot what you have going on >> > now, here's some places to start: >> > - you're missing files... figure out which package is supposed to >> > provide them and install it >> >> He misses LaTeX format file itself, and apparently mktexfmt (which >> should create it) cannot be found. This seems more serious than what >> you write. >> >> > - check your paths >> >> Agreed, but this may be quite subtle... >> >> Best, >> >> -- >> Marcin Borkowski >> http://mbork.pl >> >> > > -- > regards, > > Tim > > -- > Tim Cross > -- The Kafka Pandemic What is misopathy? https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html The disease DOES progress. MANY people have died from it. And ANYBODY can get it at any time.
