Re: [O] Colon in block name?
Hi Eric, Eric S Fraga writes: > On Thursday, 12 Feb 2015 at 16:19, Loris Bennett wrote: >> Hi, >> >> I want to export to LaTeX and refer to tables and code blocks as in the >> example below. However a name with a colon, such as 'tab:my_data' used >> as a variable for a source block fails: >> >> org-babel-ref-resolve: Reference 'my_data' not found in this buffer > > The problem is that you need to get rid of the empty lines between the > table information (name, caption) and the actual table: > >> My data can be found in Table [[tab:my_data]]. >> >> #+CAPTION: My data >> #+NAME: tab:my_data >> >> | a | b | >> |---+---| >> | 2 | 4 | >> | 3 | 9 | > > Delete the line after the #+name and it will work: if you look at the > LaTeX, you'll see a table environment around the tabular structure and > that's needed to get labels that you can referece. > > Not sure why the empty line matters, mind you... > > HTH, > eric In my ECM and in my original posting there are no empty lines between the table information and the actual table (see attached screenshot of my original ECM). However, I can see that in your quoted version above there is one. It seems as if at some point extraneous lines are being inserted into my original posting, although it looks all right to me. Or it's a case of the Inverse Emperor's New Newlines and I am too foolish to see them ... Cheers, Loris -- This signature is currently under construction.
Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'
Allow me to revisit this thread in a week or 10 days so that I can 1. take a look at ODF standard. 2. dig in to LibreOffice discussion lists to see whether such instances have ever surfaced (and how they were dealt with). Until then, please keep the patch in waiting. On Friday 13 February 2015 05:48 AM, Nicolas Goaziou wrote: Vaidheeswaran writes: What changes need to be made in ox.el and/or ox-odt.el so that the snippet I shared produces the right XML acceptable for LibreOffice. text1 [fn:1] text2 [fn:2] [fn:1] footdef1[fn:2] [fn:2] footdef2 For purposes of ODT backend, we need to find the 'site of first reference' THAT IS OUTSIDE OF A foonote definition. I think the following should work (defun org-odt-footnote-first-reference-p (footnote-reference info) "Non-nil when FOOTNOTE-REFERENCE is the first one for its label. INFO is a plist containing current export state. Unlike to `org-export-footnote-first-reference-p', this function ignores footnote definitions. As a consequence, it assumes that for a given label, there is at least one footnote reference outside any footnote definition in the document." (let ((label (org-element-property :label footnote-reference))) (or (not label) (eq footnote-reference (org-element-map (plist-get info :parse-tree) 'footnote-reference (lambda (fn) (and (equal (org-element-property :label fn) label) fn)) info t 'footnote-definition) Would it be possible for you to augment the API so that I can request such a reference. I'd rather not change the API, as this makes an unnecessary assumption. Note that `org-export-get-footnote-number' also assumes the same. E.g. text1 [fn:foo] text2 [fn:quux] text3 [fn:bar] [fn:foo] footdeffoo[fn:bar] [fn:bar] footdefbar [fn:quux] footdefquux NOTE: The XML that is emitted by the ODT exporter, suggests that the '[fn:2]' occurring in '[fn:1]' is treated as site of first reference. We would like to make '[fn:2]' occurring next to 'text2' be treated as the site of first reference. If we do that, everything will be just right. If the function above works for your use case, I'll install a patch in ox-odt. Regards,
[O] [org-drill] Suggestion to fix the drop of org-end-of-meta-data-and-drawers
Hi, since the drop of org-end-of-meta-data-and-drawers contrib/org-drill fails in master. AFAICT a possible fix is: #v+ diff --git a/contrib/lisp/org-drill.el b/contrib/lisp/org-drill.el index a0d33aa..8154904 100644 --- a/contrib/lisp/org-drill.el +++ b/contrib/lisp/org-drill.el @@ -1708,7 +1708,7 @@ Note: does not actually alter the item." (org-back-to-heading t) (let ((lim (save-excursion (outline-next-heading) (point - (org-end-of-meta-data-and-drawers) + (org-end-of-meta-data t) (or (>= (point) lim) (null (re-search-forward "[[:graph:]]" lim t)) #v- Is it sufficient to apply this fix to master? Am I missing something? Best regards, Marco -- http://www.wahlzone.de GPG: 0x49010A040A3AE6F2
Re: [O] Citations, continued
On Wed, Feb 11, 2015 at 11:51 AM, Richard Lawrence < richard.lawre...@berkeley.edu> wrote: > Stefan Nobis writes: > > > Richard Lawrence writes: > > > > But anyway: Some tool is needed to generate the bibliography with all > > its data - this tool has to handle all these details and therefore it > > should be not too hard to get partial data from it. > > That is true. Some tool does have to do this, and there are tools that > are designed for it outside of LaTeX (like CSL processors) that Org > could rely on. But I really don't have any idea how easy it would be to > make the exporter interact with them in a fine-grained way like this, or > what constraints they would place on citation support in Org. Does > anyone have a sense of this? > > I think Erik Hetzner knows a lot about this -- he has done all that work on zotxt, which involves talking to Zotero's internal citeproc.js, which is, I think, the most widely-used CSL processor. Matt
Re: [O] closing column mode for beamer export
Eric S Fraga ucl.ac.uk> writes:
> On Wednesday, 11 Feb 2015 at 11:46, L.Larrabee Strow wrote:
> > Here is the simplest example I can come up with. I changed the four
> > figures to text. Note that in comments, I show where I can add
> > \end{columns} and \begin{columns} to the org-generated .tex files, and I
> > get what I want, a 2x2 set of figures.
>
> Thanks.
>
> I can get this to work by inserting an empty "non-column" block with
> heading ignored between the two pairs of blocks, as in the attached:
Again, this is a hack. Beamer export has the :B_columns: tag for exactly
this purpose.
hjh
[O] Please help to CBSE RESIDENTIAL SCHOOL Building Grant or Donation
Re: [O] How to include time when generating timestamp for DEADLINE/SCHEDULE
PS It is clear that you can *both* select the correct date using calendar, and *then* type in the time while still in the calendar selector, right? On Thu, Feb 12, 2015 at 5:36 PM, Yuri Niyazov wrote: > On Thu, Feb 12, 2015 at 4:16 PM, Subhan Michael Tindall > wrote: >> Not really an acceptable answer. Having to use 2 different interface methods >> to fill in one time/date stamp value is confusing and cludgy. Plus, if you >> type in a full time/date stamp + time, you can still move around in the >> calendar, but it doesn't update the selected datestamp in yellow. Also >> confusing. > > Cludgy is in the eye of the beholder. I am hugely bothered by various > inconsistencies in org-mode user interface (see my other posts to this > list) but this one is very far down on the list. This is why: > > When I need to schedule a date, it is sufficiently close to today's > date that it is usually 2-3 S+ARROWS keystrokes away from today, so > the calendar with "today" selected as default is great. > > So, let's see how a time selector would work: > > When you bring up a time selector, it could by default show one of the > following three options: > > 1) The current time > 2) The last time you selected when you used the time selector > 3) Some default configurable time like "noon" > > When I need to schedule a time for an event, the time that something > needs to happen is usually not related to any times on that list, so > using S+ARROWS would be less efficient than typing out the time, which > is at most four keystrokes if its on the hour. (E.g. "10pm" ). Of > course, this is only true if you are a touch-typist.
Re: [O] How to include time when generating timestamp for DEADLINE/SCHEDULE
On Thu, Feb 12, 2015 at 4:16 PM, Subhan Michael Tindall wrote: > Not really an acceptable answer. Having to use 2 different interface methods > to fill in one time/date stamp value is confusing and cludgy. Plus, if you > type in a full time/date stamp + time, you can still move around in the > calendar, but it doesn't update the selected datestamp in yellow. Also > confusing. Cludgy is in the eye of the beholder. I am hugely bothered by various inconsistencies in org-mode user interface (see my other posts to this list) but this one is very far down on the list. This is why: When I need to schedule a date, it is sufficiently close to today's date that it is usually 2-3 S+ARROWS keystrokes away from today, so the calendar with "today" selected as default is great. So, let's see how a time selector would work: When you bring up a time selector, it could by default show one of the following three options: 1) The current time 2) The last time you selected when you used the time selector 3) Some default configurable time like "noon" When I need to schedule a time for an event, the time that something needs to happen is usually not related to any times on that list, so using S+ARROWS would be less efficient than typing out the time, which is at most four keystrokes if its on the hour. (E.g. "10pm" ). Of course, this is only true if you are a touch-typist.
Re: [O] Announcement: org-one-to-many
I think it doesn't matter where they go. I usally put them at the top, but sometimes at the bottom, sometimes in a section I mark noexport to keep them out of the way. It depends on whether someone should actually read them, or if this is just an intermediate to an end. Marcin Borkowski writes: > On 2015-02-13, at 00:43, John Kitchin wrote: > >> I think it would be easy to copy all the file keywords. One way would >> just be searching by regexp. Another way could be similar to: >> >> http://kitchingroup.cheme.cmu.edu/blog/2013/05/05/Getting-keyword-options-in-org-files/ >> >> if you know in advance what the important ones are. > > Thanks for your input! > > OTOH, /getting/ keywords/options is only one half of the problem, the > other half being is /putting/ them in some place. Personally, I think > putting them in the section of their own might be a good idea. > > Best, -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'
Vaidheeswaran writes: > What changes need to be made in ox.el and/or ox-odt.el so that the > snippet I shared produces the right XML acceptable for LibreOffice. > > text1 [fn:1] > > text2 [fn:2] > > [fn:1] footdef1[fn:2] > > [fn:2] footdef2 > > For purposes of ODT backend, we need to find the 'site of first > reference' THAT IS OUTSIDE OF A foonote definition. I think the following should work (defun org-odt-footnote-first-reference-p (footnote-reference info) "Non-nil when FOOTNOTE-REFERENCE is the first one for its label. INFO is a plist containing current export state. Unlike to `org-export-footnote-first-reference-p', this function ignores footnote definitions. As a consequence, it assumes that for a given label, there is at least one footnote reference outside any footnote definition in the document." (let ((label (org-element-property :label footnote-reference))) (or (not label) (eq footnote-reference (org-element-map (plist-get info :parse-tree) 'footnote-reference (lambda (fn) (and (equal (org-element-property :label fn) label) fn)) info t 'footnote-definition) > Would it be possible for you to augment the API so that I can request > such a reference. I'd rather not change the API, as this makes an unnecessary assumption. Note that `org-export-get-footnote-number' also assumes the same. E.g. text1 [fn:foo] text2 [fn:quux] text3 [fn:bar] [fn:foo] footdeffoo[fn:bar] [fn:bar] footdefbar [fn:quux] footdefquux > NOTE: The XML that is emitted by the ODT exporter, suggests that the > '[fn:2]' occurring in '[fn:1]' is treated as site of first reference. > We would like to make '[fn:2]' occurring next to 'text2' be treated as > the site of first reference. If we do that, everything will be just > right. If the function above works for your use case, I'll install a patch in ox-odt. Regards,
Re: [O] Announcement: org-one-to-many
On 2015-02-13, at 00:43, John Kitchin wrote: > I think it would be easy to copy all the file keywords. One way would > just be searching by regexp. Another way could be similar to: > > http://kitchingroup.cheme.cmu.edu/blog/2013/05/05/Getting-keyword-options-in-org-files/ > > if you know in advance what the important ones are. Thanks for your input! OTOH, /getting/ keywords/options is only one half of the problem, the other half being is /putting/ them in some place. Personally, I think putting them in the section of their own might be a good idea. Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
Re: [O] [patch, ox-latex] better hyperref and title options
Hello,
Rasmus writes:
> This patch does two things.
>
> 1. Add better format-spec to ox-latex hyperref and title-command.
> 2. Use this to extend basic hyperref formatting to include title,
> author, language etc.
>
> Wrt the title-command, this is useful if you need one-off "custom"
> formatting of a header in LaTeX, e.g. in ox-publish projects.
OK.
> (defcustom org-latex-title-command "\\maketitle"
>"The command used to insert the title just after \\begin{document}.
> -If this string contains the formatting specification \"%s\" then
> -it will be used as a formatting string, passing the title as an
> -argument."
> +
> +A number of formatting keys can be used to construct the command.
> +See `org-latex-format-spec'."
Since this is a defcustom, I think formatting keys should be listed in
full in its docstring.
> (defcustom org-latex-hyperref-template
> - "\\hypersetup{\n pdfkeywords={%k},\n pdfsubject={%d},\n
> pdfcreator={%c}}\n"
> + "\\hypersetup{\n pdfauthor={%a},\n pdftitle={%t},\n pdfkeywords={%k},
> + pdfsubject={%d},\n pdfcreator={%c}, \n pdflang={%l}}\n"
>"Template for hyperref package options.
>
> -Value is a format string, which can contain the following placeholders:
> -
> - %k for KEYWORDS line
> - %d for DESCRIPTION line
> - %c for CREATOR line
> +See `org-latex-format-spec' for placeholder keys.
Ditto.
> +(defun org-latex-format-spec (info)
> + "Create a format-spec for e.g. `org-latex-hyperref-template'.
> +
> +Value is a format string, which can contain the following placeholders:
> +
> + %a for AUTHOR keyword
> + %t for TITLE keyword
> + %k for KEYWORDS line
> + %d for DESCRIPTION line
> + %c for CREATOR line
> + %l for Language keyword
> + %D for DATE keyword"
> +
> + `((?a . ,(or (org-export-data (plist-get info :author) info) ""))
> +(?t . ,(or (org-export-data (plist-get info :title) info) ""))
> +(?k . ,(or (plist-get info :keywords) ""))
> +(?d . ,(or (plist-get info :description) ""))
> +(?c . ,(if (plist-get info :with-creator) (plist-get info :creator) ""))
> +(?l . ,(or (plist-get info :language) ""))
> +(?D . ,(org-export-data (org-export-get-date info) info
Please rename it `org-latex--format-spec', this is clearly an internal
function.
Also, its docstring should refer to INFO parameter.
> + (let ((template (plist-get info :latex-hyperref-template)))
> + (and (stringp template)
> +(format-spec template
> + (org-latex-format-spec info
> ;; Document start.
> "\\begin{document}\n\n"
> ;; Title command.
> - (let ((command (plist-get info :latex-title-command)))
> + (let* ((title-command (plist-get info :latex-title-command))
> +(command (and (stringp title-command)
> + (format-spec title-command
> + (org-latex-format-spec info)
This is sub-optimal: you're building the spec twice. I suggest to use a
(let ((spec (org-latex--format-spec info
somewhere above.
You can apply the changes once these issues are resolved.
Thank you.
Regards,
--
Nicolas Goaziou
Re: [O] How to obtain the list of files included in HTML export?
In https://github.com/jkitchin/jmax/blob/master/ox-archive.el you can see how I have done something like this for emailing and creating zip files. It might give you some hints that help your case. Marcin Borkowski writes: > Hi there again, > > the subject pretty much says it all. Apart from the HTML file itself > there might be inlined images and bitmaps of equations. Since I'd like > to make my customized exporter create a self-contained zip file, I need > the list of all files comprising the generated web page. > > Best, -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] [PATCH]: BUG fix and Add header-args property to source block info
Rainer M Krug writes: > I think I will skip the bonus points this time - sorry. OK. You may also send me a couple of ECM, so I can turn them into tests. > I would be very grateful if you could submit the patch without a test. Applied. Thank you. Regards.
Re: [O] Announcement: org-one-to-many
I think it would be easy to copy all the file keywords. One way would just be searching by regexp. Another way could be similar to: http://kitchingroup.cheme.cmu.edu/blog/2013/05/05/Getting-keyword-options-in-org-files/ if you know in advance what the important ones are. Marcin Borkowski writes: > Hello everybody, > > so I've got this little library of mine, called org-one-to-many, which > can split an Org file into pieces, modifying internal links so that they > still point to the same place (even if now in another file). > > But I have a problem with it. I would like to export all the resulting > files into, say, HTML, and the problem is that all the options > (obviously) don't propagate to the “subfiles” – so that if I say e.g. > > #+LANGUAGE: pl > > anywhere in the file, it is not copied to all the resulting files > (generated from headings), unless this line happens to be in one of them > (and then it disappears from the “main” file). > > I can see two solutions to this problem. One is to somehow recognize > these lines and copy them to all the resulting files. One trouble with > that is that I’d have to decide, for instance, /where/ to put them – at > the beginning? > > The easier solution, which /might/ also be “cleaner” in a sense, is to > recognize some kind of “special” heading - for instance, > > * COMMENT Config > #+LANGUAGE: pl > > or something like that, and copy it verbatim to all the generated files, > say – at their end. > > What do you think? Can you see another solution? If not, which of the > above do you consider a better one? > > TIA, -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] Question on org-publish-find-date
Hello, Rasmus writes: > In org-publish-find-date there's a clause: > >(eq (org-element-type date) 'timestamp) > > where date is extracted from (org-export-get-environment). > > Is this clause /ever/ true? In my experience even single time stamps are > on the from ((timestamp ...)). Correct. I removed the useless branch. Thank you. Regards, -- Nicolas Goaziou
[O] How to obtain the list of files included in HTML export?
Hi there again, the subject pretty much says it all. Apart from the HTML file itself there might be inlined images and bitmaps of equations. Since I'd like to make my customized exporter create a self-contained zip file, I need the list of all files comprising the generated web page. Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
Re: [O] How to include time when generating timestamp for DEADLINE/SCHEDULE
> -Original Message- > From: emacs-orgmode-bounces+subhant=familycareinc@gnu.org > [mailto:emacs-orgmode-bounces+subhant=familycareinc@gnu.org] On > Behalf Of Dominic Surano > Sent: Thursday, February 12, 2015 12:47 PM > To: emacs-orgmode@gnu.org > Subject: Re: [O] How to include time when generating timestamp for > DEADLINE/SCHEDULE > > Subhan Michael Tindall familycareinc.org> writes: > > > > > > > > > Both C-c C-d (deadline) and C-d C-s (schedule) bring up a calendar in > the mini-buffer to pick a date > > This is great > > However, there doesn’t appear to be any way to include a time in the > deadline without going in afterwards and manually editing it. > > > > This is not so great. > > > > I would dearly love to be able to easily enter in deadlines for items > with a full date/time stamp. I frequently need to know that item X is not > only > due tomorrow (DEADLINE: <2015-02-13 Fri>). But that it is due tomorrow at > 1:00 PM (DEADLINE: > > <2015-02-13 Fri 13:00>) > > Manually editing to add the time stamp seems to cause no problems, and > causes DEADLINES to locate in the time grid as expected, which is very > helpful. > > Am I just missing something, or is this a glaring hole in the > scheduling mechanic? > > Thanks! > > Subhan > > > > > > I believe you're missing something. While in the Date+time mini-buffer, you > can enter a string such as "2015-02-03 1:00pm" or "2015-04-21 13:50" > rather than just S+ARROWS to select the day. The yellow highlighted text will > update accordingly to reflect how it's interpreting your input. > Pressing enter should insert the deadline / scheduled date AND time. [>] Not really an acceptable answer. Having to use 2 different interface methods to fill in one time/date stamp value is confusing and cludgy. Plus, if you type in a full time/date stamp + time, you can still move around in the calendar, but it doesn't update the selected datestamp in yellow. Also confusing. I use the calendar to select a date, it works wonderfully, and quickly. But, once a date is picked, having either a prompt or a simple picker that works with the S+ARROWS to select a time would be great, and make a much smoother interface. This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you.
Re: [O] Announcement: org-one-to-many
Hello everybody, so I've got this little library of mine, called org-one-to-many, which can split an Org file into pieces, modifying internal links so that they still point to the same place (even if now in another file). But I have a problem with it. I would like to export all the resulting files into, say, HTML, and the problem is that all the options (obviously) don't propagate to the “subfiles” – so that if I say e.g. #+LANGUAGE: pl anywhere in the file, it is not copied to all the resulting files (generated from headings), unless this line happens to be in one of them (and then it disappears from the “main” file). I can see two solutions to this problem. One is to somehow recognize these lines and copy them to all the resulting files. One trouble with that is that I’d have to decide, for instance, /where/ to put them – at the beginning? The easier solution, which /might/ also be “cleaner” in a sense, is to recognize some kind of “special” heading - for instance, * COMMENT Config #+LANGUAGE: pl or something like that, and copy it verbatim to all the generated files, say – at their end. What do you think? Can you see another solution? If not, which of the above do you consider a better one? TIA, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
Re: [O] How to include time when generating timestamp for DEADLINE/SCHEDULE
Subhan Michael Tindall familycareinc.org> writes: > > > > Both C-c C-d (deadline) and C-d C-s (schedule) bring up a calendar in the mini-buffer to pick a date > This is great > However, there doesn’t appear to be any way to include a time in the deadline without going in afterwards and manually editing it. > > This is not so great. > > I would dearly love to be able to easily enter in deadlines for items with a full date/time stamp. I frequently need to know that item X is not only due tomorrow (DEADLINE: <2015-02-13 Fri>). But that it is due tomorrow at 1:00 PM (DEADLINE: > <2015-02-13 Fri 13:00>) > Manually editing to add the time stamp seems to cause no problems, and causes DEADLINES to locate in the time grid as expected, which is very helpful. > Am I just missing something, or is this a glaring hole in the scheduling mechanic? > Thanks! > Subhan > > > This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you. I believe you're missing something. While in the Date+time mini-buffer, you can enter a string such as "2015-02-03 1:00pm" or "2015-04-21 13:50" rather than just S+ARROWS to select the day. The yellow highlighted text will update accordingly to reflect how it's interpreting your input. Pressing enter should insert the deadline / scheduled date AND time.
Re: [O] How to include time when generating timestamp for DEADLINE/SCHEDULE
you can just type in the time in the mini buffer. On Thu, Feb 12, 2015 at 12:17 PM, Subhan Michael Tindall wrote: > Both C-c C-d (deadline) and C-d C-s (schedule) bring up a calendar in the > mini-buffer to pick a date > > This is great > > However, there doesn’t appear to be any way to include a time in the > deadline without going in afterwards and manually editing it. > > This is not so great. > > > > I would dearly love to be able to easily enter in deadlines for items with a > full date/time stamp. I frequently need to know that item X is not only due > tomorrow (DEADLINE: <2015-02-13 Fri>). But that it is due tomorrow at 1:00 > PM (DEADLINE: <2015-02-13 Fri 13:00>) > > Manually editing to add the time stamp seems to cause no problems, and > causes DEADLINES to locate in the time grid as expected, which is very > helpful. > > Am I just missing something, or is this a glaring hole in the scheduling > mechanic? > Thanks! > > Subhan > > > > > This message is intended for the sole use of the individual and entity to > which it is addressed and may contain information that is privileged, > confidential and exempt from disclosure under applicable law. If you are not > the intended addressee, nor authorized to receive for the intended > addressee, you are hereby notified that you may not use, copy, disclose or > distribute to anyone the message or any information contained in the > message. If you have received this message in error, please immediately > advise the sender by reply email and delete the message. Thank you.
Re: [O] And another useful function for header arguments
On Thu, Feb 12, 2015 at 1:58 AM, Rainer M Krug wrote: > I think I should read the manual - but who does this actually ;-) ? That is the cool part. You don't have to read the whole manual. Not even a whole page! Just a brief list and that is all it takes to start having *more* fun with org!
[O] How to include time when generating timestamp for DEADLINE/SCHEDULE
Both C-c C-d (deadline) and C-d C-s (schedule) bring up a calendar in the mini-buffer to pick a date This is great However, there doesn't appear to be any way to include a time in the deadline without going in afterwards and manually editing it. This is not so great. I would dearly love to be able to easily enter in deadlines for items with a full date/time stamp. I frequently need to know that item X is not only due tomorrow (DEADLINE: <2015-02-13 Fri>). But that it is due tomorrow at 1:00 PM (DEADLINE: <2015-02-13 Fri 13:00>) Manually editing to add the time stamp seems to cause no problems, and causes DEADLINES to locate in the time grid as expected, which is very helpful. Am I just missing something, or is this a glaring hole in the scheduling mechanic? Thanks! Subhan This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you.
Re: [O] [PATCH]: BUG fix and Add header-args property to source block info
On Thu, 12 Feb 2015, Rainer M Krug wrote: Rainer M Krug writes: Nicolas Goaziou writes: Hello, Rainer M Krug writes: Please find attached the below described patch including the fix for the error reported - function raises error when property value is numeric. Looks good. Thank you. Thanks. Could you provide an appropriate commit message? Here is the patch attached with the commit message - hope it is OK. Bonus points if you also add a test. I think I will skip the bonus points this time - sorry. I would be very grateful if you could submit the patch without a test. Cheers, Rainer Are there some guidelines on how to write tests? Never done this before... Alan's suggestions are good. To which I might add browse `testing/README'. Try this. Evaluate these blocks: #+BEGIN_SRC emacs-lisp :var here=(buffer-file-name) (add-to-list 'load-path (file-name-directory here)) (require 'org-test) #+END_SRC #+BEGIN_SRC emacs-lisp (ert-deftest test-org-babel/view-src-block-info-for-identity () "Check `(identity #o444)' in header-args property." (org-test-with-temp-text "#+PROPERTY: header-args :tangle-mode (identity #o444) ,#+begin_src emacs-lisp (+ 1 2) ,#+end_src" (org-mode-restart) (forward-line 2) (org-babel-view-src-block-info))) #+END_SRC Then do ` M-x ert RET t RET' and a window should pop up showing that you either passed (with your patch) or failed (without your patch) 1 test. If that much works, then submit a patch for testing/lisp/test-ob.el. HTH, Chuck
Re: [O] tasks, clocks, and notes
Try '(org-log-note-clock-out t) This gives you something like this: * WORK break This is my break log CLOCK: [2015-02-04 Wed 11:20]--[2015-02-04 Wed 11:30] => 0:10 - coffee CLOCK: [2015-02-04 Wed 09:52]--[2015-02-04 Wed 10:16] => 0:24 - coffee, walk CLOCK: [2015-02-03 Tue 09:35]--[2015-02-03 Tue 09:45] => 0:10 - walk Now, now to get a coherent report out of them other than by looking at the TODO is not something I've worked out yet > -Original Message- > From: emacs-orgmode-bounces+subhant=familycareinc@gnu.org > [mailto:emacs-orgmode-bounces+subhant=familycareinc@gnu.org] On > Behalf Of hymie! > Sent: Thursday, February 12, 2015 8:07 AM > To: emacs-orgmode@gnu.org > Subject: [O] tasks, clocks, and notes > > Greetings. > > I have a funny feeling I asked this before, but I can't remember and I > couldn't > find it in a search. > > So let's say I have a task -- fix a computer. I add some memory, I test the > new memory and that doesn't solve the problem, and then I finally figure out > it was the video driver. > > I could log that this way: > > * fix the computer > ** added memory to the machine > CLOCK: [2015-01-28 Wed 12:36] -- [2015-01-28 Wed 13:14] > ** memory didn't resolve the problem > CLOCK: [2015-01-28 Wed 13:28] -- [2015-01-28 Wed 13:53] > ** finally found it -- it was the video driver > CLOCK: [2015-01-29 Thu 09:12] -- [2015-01-29 The 11:30] > > but then my Agenda will have pretty disjoint notes about "added memory to > the machine". I'd prefer that the Agenda either say "fix the computer" > or (even better) "fix the computer -- added memory to the machine". > > Is there something I can do that would add "notes" to an individual clock > entry, something like > > * fix the computer > CLOCK: [2015-01-28 Wed 12:36] -- [2015-01-28 Wed 13:14] > added memory to the machine > CLOCK: [2015-01-28 Wed 13:28] -- [2015-01-28 Wed 13:53] > memory didn't resolve the problem > CLOCK: [2015-01-29 Thu 09:12] -- [2015-01-29 The 11:30] > finally found it -- it was the video driver > > that would still leave the clock lines "attached" to the main task, but still > keep > some individual notes about the various pieces of the task? > > --hymie! > This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you.
[O] Question on org-publish-find-date
Hi, In org-publish-find-date there's a clause: (eq (org-element-type date) 'timestamp) where date is extracted from (org-export-get-environment). Is this clause /ever/ true? In my experience even single time stamps are on the from ((timestamp ...)). —Rasmus -- Lasciate ogni speranza, voi che leggete questo.
Re: [O] ODT export: Issues with `org-export-footnote-first-reference-p'
Aloha Vaidheeswaran, Thanks very much for the detailed response and the link to the book. That's an interesting example I won't soon forget. The forward reference in the footnote is unusual. In this case it appears to be standing in for the lack of an index entry for either "trichiliocosm" or "chiliocosm." It's eye opening to see Org mode at work so deep in the humanities. All the best, Tom Vaidheeswaran C writes: > On Thursday 12 February 2015 12:49 PM, Thomas S. Dye wrote: >> Aloha Vaidheeswaran, >> >> This is an odd example that I don't recall having seen in any >> publication. I don't doubt examples might exist, but don't remember >> having seen one. Can you point me to a real-world example of a footnote >> referring to a subsequent footnote that I might reference either on-line >> or in my local library? > > I am OCRing this book: > http://wenshuchan-online.weebly.com/uploads/9/4/8/2/9482304/chan-and-zen-teachingpdf.pdf. > This book is atleast 50 years old. > > You can find the converted files here: > https://archive.org/details/TheDiamondCutterOfDoubts > > > The actual text extract goes something as below. I am attaching the > scanned image of the book in question. > > > > > # page 159 > > Now they saw uncountable and limitless numbers of living beings in the > universe[fn:145-1] and wondered when all these beings could be saved > and how they could obtain the Buddha fruit since the universe would > never be emptied of these beings. > > > # page 169 > > #+BEGIN_QUOTE > > 'Subhuti, what do you think? If someone filled the Universe[fn:155-4] > with the seven treasures[fn:155-5] and gave them all as alms, would > his merit be great? > > Subhuti replied: 'Very great, World Honoured One. Why? Because this > merit is not the nature of merit, the Tathagata says it is > great.[fn:155-6] > > Subhuti, if on the other hand, someone received and kept even a four > line stanza of this sutra and expounded it to others, his merit would > surpass that (of the giver of treasures). Why? (Because), Subhuti, all > Buddhas and their Supreme-Enlightenment-Dharma originate from this > sutra. Subhuti, the so-called Buddhas and Dharmas are not real Buddhas > and Dharmas.'[fn:155-7] > > #+END_QUOTE > > [fn:145-1] Literally ‘the great trichiliocosm’. See footnote 4, p. > 169.[fn:155-4] > > [fn:155-4] Tri-sahasra-maha-sahasra-loka-dhatu=a great > trichiliocosm. Mt. Sumeru and its seven surrounding continents, eight > seas and ring of iron mountains form one small world; 1,000 of these > form a small chiliocosm; 1,000 of these small chiliocosms form a > medium chiliocosm; 1,000 of these form a great chiliocosm, which > consists of 1,000,000,000 small worlds. The word ‘universe’ is used > for convenience sake. > > > > > >> All the best, >> Tom >> >> Vaidheeswaran writes: >> >>> On Thursday 12 February 2015 02:42 AM, Nicolas Goaziou wrote: It does, e.g., when exporting to LaTeX. This is an odt limitation. So, I disagree, `org-export-footnote-first-reference-p' is correct here. >>> >>> >>> Let me put my question this way: >>> >>> What changes need to be made in ox.el and/or ox-odt.el so that the >>> snippet I shared produces the right XML acceptable for LibreOffice. >>> >>> text1 [fn:1] >>> >>> text2 [fn:2] >>> >>> [fn:1] footdef1[fn:2] >>> >>> [fn:2] footdef2 >>> >>> For purposes of ODT backend, we need to find the 'site of first >>> reference' THAT IS OUTSIDE OF A foonote definition. Would it be >>> possible for you to augment the API so that I can request such a >>> reference. >>> >>> NOTE: The XML that is emitted by the ODT exporter, suggests that the >>> '[fn:2]' occurring in '[fn:1]' is treated as site of first >>> reference. We would like to make '[fn:2]' occurring next to 'text2' be >>> treated as the site of first reference. If we do that, everything >>> will be just right. >>> >>> >>> >>> >>> >> > > -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] Latex code before maketitle
On Wed Feb 11 2015 at 4:01:47 PM Rasmus wrote:
> Maybe something like AfterPreamble, AfterEndPreamble, AtEndPreamble etc.
> from etoolbox?
Ah, a Latex solution to an Org problem. I was looking for a final filter
and didn't realize it, but used your approach before I saw Chuck's reply.
Since I was already defining a custom org-latex-class, I was able to add
the necessary code inside the class definition:
(add-to-list 'org-latex-classes
...
[NO-DEFAULT-PACKAGES]
[EXTRA]
\\AfterPreamble{
...
}
This works great.
On Wed Feb 11 2015 at 7:24:43 PM Charles C. Berry wrote:
> (info "(org) Advanced configuration") has a heading called 'Filters' that
> may interest you.
>
Indeed, this is what I was missing. I would have used this if I hadn't
already figured it out with AfterPreamble
I started creating a filter to move the TOC (which I need to come after
"Acknowledgments"), but it turned out to be easier just to set toc:nil and
put the TOC and lists of figures/tables where I wanted them as raw Latex
commands
Thanks both for the help.
Regards,
Jake
[O] tasks, clocks, and notes
Greetings. I have a funny feeling I asked this before, but I can't remember and I couldn't find it in a search. So let's say I have a task -- fix a computer. I add some memory, I test the new memory and that doesn't solve the problem, and then I finally figure out it was the video driver. I could log that this way: * fix the computer ** added memory to the machine CLOCK: [2015-01-28 Wed 12:36] -- [2015-01-28 Wed 13:14] ** memory didn't resolve the problem CLOCK: [2015-01-28 Wed 13:28] -- [2015-01-28 Wed 13:53] ** finally found it -- it was the video driver CLOCK: [2015-01-29 Thu 09:12] -- [2015-01-29 The 11:30] but then my Agenda will have pretty disjoint notes about "added memory to the machine". I'd prefer that the Agenda either say "fix the computer" or (even better) "fix the computer -- added memory to the machine". Is there something I can do that would add "notes" to an individual clock entry, something like * fix the computer CLOCK: [2015-01-28 Wed 12:36] -- [2015-01-28 Wed 13:14] added memory to the machine CLOCK: [2015-01-28 Wed 13:28] -- [2015-01-28 Wed 13:53] memory didn't resolve the problem CLOCK: [2015-01-29 Thu 09:12] -- [2015-01-29 The 11:30] finally found it -- it was the video driver that would still leave the clock lines "attached" to the main task, but still keep some individual notes about the various pieces of the task? --hymie!
Re: [O] Colon in block name?
On Thursday, 12 Feb 2015 at 16:19, Loris Bennett wrote: > Hi, > > I want to export to LaTeX and refer to tables and code blocks as in the > example below. However a name with a colon, such as 'tab:my_data' used > as a variable for a source block fails: > > org-babel-ref-resolve: Reference 'my_data' not found in this buffer The problem is that you need to get rid of the empty lines between the table information (name, caption) and the actual table: > My data can be found in Table [[tab:my_data]]. > > #+CAPTION: My data > #+NAME: tab:my_data > > | a | b | > |---+---| > | 2 | 4 | > | 3 | 9 | Delete the line after the #+name and it will work: if you look at the LaTeX, you'll see a table environment around the tabular structure and that's needed to get labels that you can referece. Not sure why the empty line matters, mind you... HTH, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-816-gae83b3
[O] Colon in block name?
Hi, I want to export to LaTeX and refer to tables and code blocks as in the example below. However a name with a colon, such as 'tab:my_data' used as a variable for a source block fails: org-babel-ref-resolve: Reference 'my_data' not found in this buffer Obviously, and perhaps not surprisingly, the use of the colon in the name seems to be problematic. Should this work? If not, is there a common alternative to the idiom tab:shootings_in_the_foot and fig:foot_with_hole? Cheers, Loris PS: In the example below, the last table is not exported to the LaTeX file, but this is presumably an unrelated issue ... Example: * Test with block names containing a colon ** Data My data can be found in Table [[tab:my_data]]. #+CAPTION: My data #+NAME: tab:my_data | a | b | |---+---| | 2 | 4 | | 3 | 9 | ** Code My code can be found in Listing [[code:my_code]]. #+CAPTION: My code #+NAME: code:my_code #+HEADER: :var data=tab:my_data :colnames yes #+BEGIN_SRC R d <- data #+END_SRC ** Results My results can be found in Table [[tab:my_results]]. #+CAPTION: My results #+NAME: tab:my_results #+RESULTS: code:my_code | a | b | |---+---| | 2 | 4 | | 3 | 9 | ** Conclusions Names with colons don't work. -- This signature is currently under construction.
Re: [O] Table formulas: daily hour * rate = cost
torys.ander...@gmail.com (Tory S. Anderson) writes: > I have the followign table, which should speak for itself. First the > "cost" column needs to be calculated, which is hours * rate, and then > the "hrs" and "ttl" fields should be filled in based on sums of their > columns. However, I'm not sure why $cost isn't being evaluated; I've > tried it with column names as well as indices but unless I specify > each field individually (e.g. @3$5) I can't get a result here. Formula > debugging seems to ignore it, too. But I've been trying to follow the > example on the "advanced feature" page[1] as closely as possible; > what's the problem? > >| | Date| Hours | Rate | Cost | >| ! | | hours | rate | cost | >|---+-+---+--+--| >| | February 9 | 4.00 | 38 |0 | >| | February 10 | 4.00 | 38 |0 | >| | February 11 | 4.00 | 38 |0 | >| | February 12 | 4.00 | 38 |0 | >| | February 13 | 4.00 | 38 |0 | >|---+-+---+--+--| >| | | 20. | |0 | >| ^ | | hrs | | ttl | >#+TBLFM: $5=$hours*$rate::$hrs=vsum(@I..@II)::$ttl=vsum(@I..@II) I have no clue why, but this table works for me; the original one does not... | | Date| Hours | Rate | Cost | | ! | | hours | rate | cost | |---+-+---+--+--| | # | February 9 | 4.00 | 38 | 152. | | # | February 10 | 4.00 | 38 | 152. | | # | February 11 | 4.00 | 38 | 152. | | # | February 12 | 4.00 | 38 | 152. | | # | February 13 | 4.00 | 38 | 152. | |---+-+---+--+--| | # | | 20. | | 760. | | ^ | | hrs | | ttl | #+TBLFM: $5=$hours*$rate::$hrs=vsum(@I..@II)::$ttl=vsum(@I..@II) -- Dobbelt-A
Re: [O] Warnings when making org from git
Rasmus writes: > Rainer M Krug writes: > >>> Thankfully, I haven't touched the orgguide.texi. But I get the same >>> warning. >> >> Lucky you... > > Enough havoc from me for one day, don't you think? (¡Sorry everybody!) There is only one last thing to say: enjoy the day from now on... Cheers Rainer > >>> BTW: make doc produces lots of warnings on my system... >> >> Are these the warnings you see? >> >> I only get them when using the homebrew version of texinfo - if I use >> the Mac version, I only get these encoding warnings. > > Below you'll find output of M-x compile make doc RET on Linux with texinfo > 5.2. I'm pretty ignorant about texi so it might be nothing... > >> So: which one is better - I can choose? > > No clue. -- Rainer M. Krug email: Rainerkrugsde PGP: 0x0F52F982 signature.asc Description: PGP signature
Re: [O] Warnings when making org from git
Rainer M Krug writes: >> Thankfully, I haven't touched the orgguide.texi. But I get the same >> warning. > > Lucky you... Enough havoc from me for one day, don't you think? (¡Sorry everybody!) >> BTW: make doc produces lots of warnings on my system... > > Are these the warnings you see? > > I only get them when using the homebrew version of texinfo - if I use > the Mac version, I only get these encoding warnings. Below you'll find output of M-x compile make doc RET on Linux with texinfo 5.2. I'm pretty ignorant about texi so it might be nothing... > So: which one is better - I can choose? No clue. -- Hooray! Title: *compilation* -*- mode: compilation; default-directory: "~/src/code/org-mode/" -*- Compilation started at Thu Feb 12 13:19:28 make doc make -C doc info make[1]: se entra en el directorio '/home/rasmus/src/code/org-mode/doc' org-version: 8.3beta (release_8.3beta-826-g4f9051) makeinfo --no-split org.texi -o org make[1]: se sale del directorio '/home/rasmus/src/code/org-mode/doc' make -C doc html make[1]: se entra en el directorio '/home/rasmus/src/code/org-mode/doc' makeinfo --html --number-sections --no-split -o org.html org.texi make[1]: se sale del directorio '/home/rasmus/src/code/org-mode/doc' make -C doc pdf make[1]: se entra en el directorio '/home/rasmus/src/code/org-mode/doc' texi2pdf --batch --clean --expand org.texi -:312: @menu seen before first @node -:312: perhaps your @top node should be wrapped in @ifnottex rather than @ifinfo? -:337: @detailmenu seen before first @node -:337: perhaps your @top node should be wrapped in @ifnottex rather than @ifinfo? -:1272: warning: @itemx should not begin @table -:1354: warning: @table has text but no @item -:1379: warning: @table has text but no @item -:1425: warning: @table has text but no @item -:1576: warning: @table has text but no @item -:1723: warning: @table has text but no @item -:2856: warning: @table has text but no @item -:2913: warning: @table has text but no @item -:3163: warning: @table has text but no @item -:4813: warning: @table has text but no @item -:4947: warning: @table has text but no @item -:5168: warning: @table has text but no @item -:5401: warning: @table has text but no @item -:5742: warning: @table has text but no @item -:6107: warning: @table has text but no @item -:6238: warning: @table has text but no @item -:6407: warning: @table has text but no @item -:6752: warning: @table has text but no @item -:6812: warning: @table has text but no @item -:6831: warning: @table has text but no @item -:6915: warning: @table has text but no @item -:7306: warning: @table has text but no @item -:7491: warning: @table has text but no @item -:7720: warning: @itemx should not begin @table -:7739: warning: @table has text but no @item -:7755: warning: @table has text but no @item -:7853: warning: @table has text but no @item -:7991: warning: @table has text but no @item -:8057: warning: @table has text but no @item -:8226: warning: @table has text but no @item -:8246: warning: @table has text but no @item -:8633: warning: @table has text but no @item -:9417: warning: @table has text but no @item -:9487: warning: @table has text but no @item -:9554: warning: @table has text but no @item -:10504: warning: @table has text but no @item -:10870: warning: @table has text but no @item -:11103: warning: @table has text but no @item -:11172: warning: @table has text but no @item -:12154: warning: @table has text but no @item -:13067: warning: @table has text but no @item -:13402: warning: @table has text but no @item -:14268: warning: @table has text but no @item -:17157: warning: @table has text but no @item -:787: warning: node `Document structure' is next for `Introduction' in sectioning but not in menu -:1148: warning: unreferenced node `Document structure' -:1148: warning: node `Tables' is next for `Document structure' in sectioning but not in menu -:1148: warning: node `Introduction' is prev for `Document structure' in sectioning but not in menu -:2068: warning: unreferenced node `Tables' -:2068: warning: node `Hyperlinks' is next for `Tables' in sectioning but not in menu -:2068: warning: node `Document structure' is prev for `Tables' in sectioning but not in menu -:3391: warning: unreferenced node `Hyperlinks' -:3391: warning: node `TODO items' is next for `Hyperlinks' in sectioning but not in menu -:3391: warning: node `Tables' is prev for `Hyperlinks' in sectioning but not in menu -:3986: warning: unreferenced node `TODO items' -:3986: warning: node `Tags' is next for `TODO items' in sectioning but not in menu -:3986: warning: node `Hyperlinks' is prev for `TODO items' in sectioning but not in menu -:4855: warning: unreferenced node `Tags' -:4855: warning: node `Properties and columns' is next for `Tags' in sectioning but not in menu -:4855: warning: node `TODO items' is prev for `Tags' in sectioning but not in menu -:5192: warning: unreferenced node `Properties and columns' -:5192: warning: node `Dates and
[O] Table formulas: daily hour * rate = cost
I have the followign table, which should speak for itself. First the "cost" column needs to be calculated, which is hours * rate, and then the "hrs" and "ttl" fields should be filled in based on sums of their columns. However, I'm not sure why $cost isn't being evaluated; I've tried it with column names as well as indices but unless I specify each field individually (e.g. @3$5) I can't get a result here. Formula debugging seems to ignore it, too. But I've been trying to follow the example on the "advanced feature" page[1] as closely as possible; what's the problem? --8<---cut here---start->8--- | | Date| Hours | Rate | Cost | | ! | | hours | rate | cost | |---+-+---+--+--| | | February 9 | 4.00 | 38 |0 | | | February 10 | 4.00 | 38 |0 | | | February 11 | 4.00 | 38 |0 | | | February 12 | 4.00 | 38 |0 | | | February 13 | 4.00 | 38 |0 | |---+-+---+--+--| | | | 20. | |0 | | ^ | | hrs | | ttl | #+TBLFM: $5=$hours*$rate::$hrs=vsum(@I..@II)::$ttl=vsum(@I..@II) --8<---cut here---end--->8--- Footnotes: [1] http://orgmode.org/org.html#Advanced-features
Re: [O] Warnings when making org from git
Rasmus writes:
> Rainer M Krug writes:
>
>> Now I get here a different warning from pdftex:
>>
>> ,
>> |
>> (/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T//t2d45050/src/orgguide.texi
>> | (/Users/rainerkrug/.emacs.d/org-git/doc/texinfo.tex
>> | Loading texinfo [version 2013-09-11.11]: pdf, fonts, markup, glyphs,
>> | page headings, tables, conditionals, indexing, sectioning, toc,
>> environments,
>> | defuns, macros, cross references, insertions,
>> | (/usr/local/texlive/2014/texmf-dist/tex/generic/epsf/epsf.tex
>> | This is `epsf.tex' v2.7.4 <14 February 2011>
>> | ) localization, formatting, and turning on texinfo input format.)
>> | (./orgguide.aux)
>> [1{/usr/local/texlive/2014/texmf-var/fonts/map/pdftex/updmap/p
>> | dftex.map}] [2] (./orgguide.toc) [-1] Chapter 1 Chapter 2 [1] [2] [3] [4]
>> | Chapter 3 [5] [6] Chapter 4 [7] [8] Chapter 5 [9] [10] [11] Chapter 6 [12]
>> | [13] Chapter 7 [14] Chapter 8 [15] [16] [17] Chapter 9 [18] [19] Chapter 10
>> | [20] [21] [22] [23] [24] Chapter 11 [25] [26] [27] Chapter 12 [28] [29]
>> | Chapter 13 [30] Chapter 14 [31] [32] Chapter 15 [33] [34] )pdfTeX warning
>> (dest
>> | ): name{36} has been referenced but does not exist, replaced by a fixed
>> | one
>> `
>
> Thankfully, I haven't touched the orgguide.texi. But I get the same
> warning.
Lucky you...
> BTW: make doc produces lots of warnings on my system...
Are these the warnings you see?
I only get them when using the homebrew version of texinfo - if I use
the Mac version, I only get these encoding warnings.
So: which one is better - I can choose?
Rainer
,
| texi2pdf --batch --clean --expand org.texi
| -:312: @menu seen before first @node
| -:312: perhaps your @top node should be wrapped in @ifnottex rather than
@ifinfo?
| -:337: @detailmenu seen before first @node
| -:337: perhaps your @top node should be wrapped in @ifnottex rather than
@ifinfo?
| -:1272: warning: @itemx should not begin @table
| -:1354: warning: @table has text but no @item
| -:1379: warning: @table has text but no @item
| -:1425: warning: @table has text but no @item
| -:1576: warning: @table has text but no @item
| -:1723: warning: @table has text but no @item
| -:2856: warning: @table has text but no @item
| -:2913: warning: @table has text but no @item
| -:3163: warning: @table has text but no @item
| -:4813: warning: @table has text but no @item
| -:4947: warning: @table has text but no @item
| -:5168: warning: @table has text but no @item
| -:5401: warning: @table has text but no @item
| -:5742: warning: @table has text but no @item
| -:6107: warning: @table has text but no @item
| -:6238: warning: @table has text but no @item
| -:6407: warning: @table has text but no @item
| -:6752: warning: @table has text but no @item
| -:6812: warning: @table has text but no @item
| -:6831: warning: @table has text but no @item
| -:6915: warning: @table has text but no @item
| -:7306: warning: @table has text but no @item
| -:7491: warning: @table has text but no @item
| -:7720: warning: @itemx should not begin @table
| -:7739: warning: @table has text but no @item
| -:7755: warning: @table has text but no @item
| -:7853: warning: @table has text but no @item
| -:7991: warning: @table has text but no @item
| -:8057: warning: @table has text but no @item
| -:8226: warning: @table has text but no @item
| -:8246: warning: @table has text but no @item
| -:8633: warning: @table has text but no @item
| -:9417: warning: @table has text but no @item
| -:9487: warning: @table has text but no @item
| -:9554: warning: @table has text but no @item
| -:10504: warning: @table has text but no @item
| -:10869: warning: @table has text but no @item
| -:11102: warning: @table has text but no @item
| -:11171: warning: @table has text but no @item
| -:12153: warning: @table has text but no @item
| -:13066: warning: @table has text but no @item
| -:13401: warning: @table has text but no @item
| -:14267: warning: @table has text but no @item
| -:17156: warning: @table has text but no @item
| -:787: warning: node `Document structure' is next for `Introduction' in
sectioning but not in menu
| -:1148: warning: unreferenced node `Document structure'
| -:1148: warning: node `Tables' is next for `Document structure' in sectioning
but not in menu
| -:1148: warning: node `Introduction' is prev for `Document structure' in
sectioning but not in menu
| -:2068: warning: unreferenced node `Tables'
| -:2068: warning: node `Hyperlinks' is next for `Tables' in sectioning but not
in menu
| -:2068: warning: node `Document structure' is prev for `Tables' in sectioning
but not in menu
| -:3391: warning: unreferenced node `Hyperlinks'
| -:3391: warning: node `TODO items' is next for `Hyperlinks' in sectioning but
not in menu
| -:3391: warning: node `Tables' is prev for `Hyperlinks' in sectioning but not
in menu
| -:3986: warning: unreferenced node `TODO items'
| -:3986: warning: node `Tags' is next for `TODO items' in sectioning but not
in menu
| -
Re: [O] Warnings when making org from git
Rainer M Krug writes:
> Now I get here a different warning from pdftex:
>
> ,
> |
> (/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T//t2d45050/src/orgguide.texi
> | (/Users/rainerkrug/.emacs.d/org-git/doc/texinfo.tex
> | Loading texinfo [version 2013-09-11.11]: pdf, fonts, markup, glyphs,
> | page headings, tables, conditionals, indexing, sectioning, toc,
> environments,
> | defuns, macros, cross references, insertions,
> | (/usr/local/texlive/2014/texmf-dist/tex/generic/epsf/epsf.tex
> | This is `epsf.tex' v2.7.4 <14 February 2011>
> | ) localization, formatting, and turning on texinfo input format.)
> | (./orgguide.aux)
> [1{/usr/local/texlive/2014/texmf-var/fonts/map/pdftex/updmap/p
> | dftex.map}] [2] (./orgguide.toc) [-1] Chapter 1 Chapter 2 [1] [2] [3] [4]
> | Chapter 3 [5] [6] Chapter 4 [7] [8] Chapter 5 [9] [10] [11] Chapter 6 [12]
> | [13] Chapter 7 [14] Chapter 8 [15] [16] [17] Chapter 9 [18] [19] Chapter 10
> | [20] [21] [22] [23] [24] Chapter 11 [25] [26] [27] Chapter 12 [28] [29]
> | Chapter 13 [30] Chapter 14 [31] [32] Chapter 15 [33] [34] )pdfTeX warning
> (dest
> | ): name{36} has been referenced but does not exist, replaced by a fixed
> | one
> `
Thankfully, I haven't touched the orgguide.texi. But I get the same
warning. BTW: make doc produces lots of warnings on my system...
—Rasmus
--
Slowly unravels in a ball of yarn and the devil collects it
Re: [O] Warnings when making org from git
Rasmus writes:
> Hi,
>
> Rainer M Krug writes:
>
>> after updating today, I saw the fiollowing errors / warnings:
>> ,
>> | org-version: 8.3beta (release_8.3beta-823-ge6fcc8)
>> | makeinfo --no-split org.texi -o org
>> | org.texi:15: warning: unrecognized encoding name `UTF-8'.
>> | org.texi:10823: @item found outside of an insertion block.
>> | org.texi:10827: Unmatched `@end'.
>> | makeinfo: Removing output file `org' due to errors; use --force to
>> preserve.
>> | make[1]: *** [org] Error 1
>> `
>
> Sorry my mistake. The org.texi should be fixed.
Yup - just the Mac typical "unrecognized encoding name `UTF-8'" left.
>
>
>> These one are, as far as i =remember, new:
>>
>> ,
>> | In org-man-template:
>> | ox-man.el:314:24:Warning: plist-get called with 1 argument, but requires 2
>> | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-man.elc
>> | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-md.el...
>> | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-md.elc
>> | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-odt.el...
>> | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-odt.elc
>> | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-org.el...
>> | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-org.elc
>> | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-publish.el...
>> | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-publish.elc
>> | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-texinfo.el...
>> |
>> | In org-texinfo-template:
>> | ox-texinfo.el:496:39:Warning: value returned from (format "@title %s
>> | " (or (plist-get info :texinfo-printed-title) title)) is unused
>> | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-texinfo.elc
>> | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox.el...
>> | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox.elc
>> `
>
> These should also be gone now.
Thanks
Now I get here a different warning from pdftex:
,
| (/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T//t2d45050/src/orgguide.texi
| (/Users/rainerkrug/.emacs.d/org-git/doc/texinfo.tex
| Loading texinfo [version 2013-09-11.11]: pdf, fonts, markup, glyphs,
| page headings, tables, conditionals, indexing, sectioning, toc, environments,
| defuns, macros, cross references, insertions,
| (/usr/local/texlive/2014/texmf-dist/tex/generic/epsf/epsf.tex
| This is `epsf.tex' v2.7.4 <14 February 2011>
| ) localization, formatting, and turning on texinfo input format.)
| (./orgguide.aux)
[1{/usr/local/texlive/2014/texmf-var/fonts/map/pdftex/updmap/p
| dftex.map}] [2] (./orgguide.toc) [-1] Chapter 1 Chapter 2 [1] [2] [3] [4]
| Chapter 3 [5] [6] Chapter 4 [7] [8] Chapter 5 [9] [10] [11] Chapter 6 [12]
| [13] Chapter 7 [14] Chapter 8 [15] [16] [17] Chapter 9 [18] [19] Chapter 10
| [20] [21] [22] [23] [24] Chapter 11 [25] [26] [27] Chapter 12 [28] [29]
| Chapter 13 [30] Chapter 14 [31] [32] Chapter 15 [33] [34] )pdfTeX warning
(dest
| ): name{36} has been referenced but does not exist, replaced by a fixed
| one
`
Cheers,
Rainer
>
> Thanks!
>
> Thanks!
--
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982
signature.asc
Description: PGP signature
Re: [O] [PATCH] Recognize property blocks even after text
Sacha Chua writes: > Hi! I noticed that the refactored org-get-property-block no longer > allows for any text (aside from the SCHEDULED / DEADLINE / CLOSED) text > between the heading and the property drawer, which gave me problems when > I accidentally added text or timestamps or things like that. Also, it > means org-gcal's default format (which puts the timestamp before the > property drawer) doesn't work, so maybe a bunch of other things rely on > the old behavior. If that part of the change was unintentional, would > you consider the patch below? It seems to be okay with my Org files, but > maybe that flexibility was removed for performance reasons. Hope this is > useful! Did you see this discussion? I think it's a feature. http://permalink.gmane.org/gmane.emacs.orgmode/91752 —Rasmus -- And I faced endless streams of vendor-approved Ikea furniture. . .
Re: [O] Warnings when making org from git
Hi, Rainer M Krug writes: > after updating today, I saw the fiollowing errors / warnings: > , > | org-version: 8.3beta (release_8.3beta-823-ge6fcc8) > | makeinfo --no-split org.texi -o org > | org.texi:15: warning: unrecognized encoding name `UTF-8'. > | org.texi:10823: @item found outside of an insertion block. > | org.texi:10827: Unmatched `@end'. > | makeinfo: Removing output file `org' due to errors; use --force to preserve. > | make[1]: *** [org] Error 1 > ` Sorry my mistake. The org.texi should be fixed. > These one are, as far as i =remember, new: > > , > | In org-man-template: > | ox-man.el:314:24:Warning: plist-get called with 1 argument, but requires 2 > | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-man.elc > | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-md.el... > | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-md.elc > | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-odt.el... > | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-odt.elc > | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-org.el... > | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-org.elc > | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-publish.el... > | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-publish.elc > | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-texinfo.el... > | > | In org-texinfo-template: > | ox-texinfo.el:496:39:Warning: value returned from (format "@title %s > | " (or (plist-get info :texinfo-printed-title) title)) is unused > | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-texinfo.elc > | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox.el... > | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox.elc > ` These should also be gone now. Thanks! -- ツ
Re: [O] [PATCH]: BUG fix and Add header-args property to source block info
Rainer M Krug writes: > Nicolas Goaziou writes: > >> Hello, >> >> Rainer M Krug writes: >> >>> Please find attached the below described patch including the fix for the >>> error reported - function raises error when property value is numeric. >> >> Looks good. Thank you. > > Thanks. > >> > > >> Could you provide an appropriate commit message? > > Here is the patch attached with the commit message - hope it is OK. > >> Bonus points if you also add a test. I think I will skip the bonus points this time - sorry. I would be very grateful if you could submit the patch without a test. Cheers, Rainer > > Are there some guidelines on how to write tests? Never done this before... > > Rainer > >> >> Regards, -- Rainer M. Krug email: Rainerkrugsde PGP: 0x0F52F982 signature.asc Description: PGP signature
Re: [O] [PATCH]: BUG fix and Add header-args property to source block info
Alan Schmitt writes: > Hello, > > On 2015-02-10 22:58, Rainer M Krug writes: > >> Are there some guidelines on how to write tests? Never done this before... > > I recently wrote my first test, so here is how I did it. > > - find a similar test in testing/lisp/el (maybe in test-ob-exp.el) > - load the file testing/org-test.el (it has many helper functions, > I needed them when testing links) > - write and evaluate your ert-deftest > - call ert to run the test > Thanks a lot. I looked at them, but I think I skip the test (and the bonus-points) this time (my limited elisp would make it quite a mission, I guess) Cheers, Rainer > Alan -- Rainer M. Krug email: Rainerkrugsde PGP: 0x0F52F982 signature.asc Description: PGP signature
[O] Warnings when making org from git
Hi, after updating today, I saw the fiollowing errors / warnings: This one is "expected" as makeinfo on Mac does not like the encoding and was here for quite some time. , | org-version: 8.3beta (release_8.3beta-823-ge6fcc8) | makeinfo --no-split org.texi -o org | org.texi:15: warning: unrecognized encoding name `UTF-8'. | org.texi:10823: @item found outside of an insertion block. | org.texi:10827: Unmatched `@end'. | makeinfo: Removing output file `org' due to errors; use --force to preserve. | make[1]: *** [org] Error 1 ` These one are, as far as i =remember, new: , | In org-man-template: | ox-man.el:314:24:Warning: plist-get called with 1 argument, but requires 2 | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-man.elc | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-md.el... | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-md.elc | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-odt.el... | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-odt.elc | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-org.el... | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-org.elc | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-publish.el... | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-publish.elc | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox-texinfo.el... | | In org-texinfo-template: | ox-texinfo.el:496:39:Warning: value returned from (format "@title %s | " (or (plist-get info :texinfo-printed-title) title)) is unused | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox-texinfo.elc | Compiling /Users/rainerkrug/.emacs.d/org-git/lisp/ox.el... | Wrote /Users/rainerkrug/.emacs.d/org-git/lisp/ox.elc ` , | Org-mode version 8.3beta (release_8.3beta-823-ge6fcc8 @/Users/rainerkrug/.emacs.d/org-mode/lisp/) | GNU Emacs 24.4.1 (x86_64-apple-darwin14.0.0, Carbon Version 157 AppKit 1343.16) of 2015-02-02 on Rainers-MacBook-Pro-4.local ` Cheers, Rainer -- Rainer M. Krug email: Rainerkrugsde PGP: 0x0F52F982 signature.asc Description: PGP signature
Re: [O] Latex code before maketitle
On Wednesday, 11 Feb 2015 at 20:42, Jacob Gerlach wrote:
> Hi List,
>
> I am using a custom Latex class that requires some code between
> \begin{document} and \maketitle.
>
> It seems from looking at ox-latex.el that there is nothing between document
> start and title command available for me to customize.
>
> I suppose I could customize the title command to include the extra code,
I don't know of any æsthetically pleasing solution to this
problem. I've done this in the past by redefining \maketitle to
introduce my design commands and then invoke the actual \maketitle
command.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-816-gae83b3
Re: [O] closing column mode for beamer export
On Wednesday, 11 Feb 2015 at 11:46, L.Larrabee Strow wrote:
> Here is the simplest example I can come up with. I changed the four
> figures to text. Note that in comments, I show where I can add
> \end{columns} and \begin{columns} to the org-generated .tex files, and I
> get what I want, a 2x2 set of figures.
Thanks.
I can get this to work by inserting an empty "non-column" block with
heading ignored between the two pairs of blocks, as in the attached:
#+LATEX_CLASS: beamer
#+LATEX_CLASS_OPTIONS: [t]
#+BEAMER_THEME: Frankfurt
#+startup: beamer
#+OPTIONS: H:2 toc:nil num:t
* Introduction
** Overview
*** first column 0.5
:PROPERTIES:
:BEAMER_col: 0.5
:END:
#+LaTeX: \centering
Figure 1 (top/left)
Text instead of figure Text instead of figure Text instead of figure
Text instead of figure Text instead of figure Text instead of figure
#+LaTeX: \vspace{0.1in}
*** second column 0.5
:PROPERTIES:
:BEAMER_col: 0.5
:END:
#+LaTeX: \centering
Figure 2 (top/right)
Text instead of figure
# If I put: \end{columns}
# and put : \begin{columns}
# here in the .tex output from org-mode, I get a 2x2 set of figures
*** Imaginary block :B_ignoreheading:
:PROPERTIES:
:BEAMER_env: ignoreheading
:END:
*** third column 0.5
:PROPERTIES:
:BEAMER_col: 0.5
:END:
#+LaTeX: \centering
Figure 3 (bottom/left)
Text instead of figure
*** fourth 0.5
:PROPERTIES:
:BEAMER_col: 0.5
:END:
#+LaTeX: \centering
Figure 4 (bottom/right)
Text instead of figure
HTH,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-816-gae83b3
