Re: [O] weird ox-odt, links and images
Nicolas Goaziou writes: > I cannot reproduce the error. However, I don't have your "cite" handler, > if that matters. I think it does. . . . I was hoping that the error output would be insightful in itself. I cut down my setup to a small example, but it's still pretty big... I works fine with html. Obviously it works fine with latex as well, but there I also don't touch formatting myself. I test from emacs -q with Org Org-mode version 8.3beta (release_8.3beta-862-gc76f25 @ /usr/share/emacs/site-lisp/org/) Instructions to ecm.org. - Install aux. files to /tmp via the first source block. - Load cite link via the second source block. - Export. On my system it exports with either elm 1 or elm 2 turned on, but not with both. - It works with ox-html. Thanks, Rasmus -- May contains speling mistake ecm.org Description: Lotus Organizer
[O] [bug?] org-repair-property-drawers does not repair whole file
Dear org-mode developers, dear Nicolas, I invoked org-repair-property-drawers on a fairly large org-mode file. It did sort some PROPERTIES drawers in front of LOGBOOK ones but not all. Since I do not understand the logic of org-repair-property-drawers I prepared a file with the structure of the org-mode file after running org-repair-property-drawers on it: egrep "^\*+|^ *:PROPERTIES:|^ *:LOGBOOK:|^ *:END:" file.org |nl >headings-properties-logbook-numbered sed -e "s/\(^ \+[0-9]\+[[:space:]]*\*\+[[:space:]]*\)\(TODO\|INPROGRESS\|WAITING\|VERIFY\|DONE\|DELEGATED\|CANCELLED\|PUTOFF\|IDEA\)*\(.*$\)/\1\2/" headings-properties-logbook-numbered >headings-properties-logbook-numbered.anon I don’t how to isolate the bug or the circumstances which trigger it. The file headings-properties-logbook-numbered.anon is attached to this email. I hope it might be useful to you to find the bug. Via grep -A2 LOGBOOK headings-properties-logbook-numbered.anon|grep PROPERTIES I can see, that there are 18 occurrences where there is a PROPERTIES drawer after a LOGBOOK drawer instead before. Some of the corresponding headings had tags, some not. And also some of the not corresponding headings had tags and some not. Ciao, Gregor -- -... --- .-. . -.. ..--.. ...-.- 1 * 2:PROPERTIES: 3:END: 4:LOGBOOK: 5:END: 6 *** DONE 7 :PROPERTIES: 8 :END: 9 :LOGBOOK: 10 :END: 11 *** INPROGRESS 12 :LOGBOOK: 13 :END: 14 *** 15 :LOGBOOK: 16 :END: 17 *** 18 :LOGBOOK: 19 :END: 20 * DONE 21:LOGBOOK: 22:END: 23 * 24 *** 25 :LOGBOOK: 26 :END: 27 * 28:LOGBOOK: 29:END: 30 * 31:LOGBOOK: 32:END: 33 *** CANCELLED 34 :LOGBOOK: 35 :END: 36 *** 37 *** 38 * DONE 39:LOGBOOK: 40:END: 41 * 42 * DONE 43 *** TODO 44 :LOGBOOK: 45 :END: 46 *** DONE 47 :LOGBOOK: 48 :END: 49 *** CANCELLED 50 :LOGBOOK: 51 :END: 52 *** DONE 53 :LOGBOOK: 54 :END: 55 * DONE 56:LOGBOOK: 57:END: 58 * DONE 59:LOGBOOK: 60:END: 61 *** PUTOFF 62 :LOGBOOK: 63 :END: 64 *** TODO 65 * 66 * 67 * 68 * 69 * 70 * 71 :LOGBOOK: 72 :END: 73 *** PUTOFF 74 :LOGBOOK: 75 :END: 76 *** DONE 77 *** TODO 78 *** INPROGRESS 79 :LOGBOOK: 80 :END: 81 *** DELEGATED 82 :PROPERTIES: 83 :END: 84 :LOGBOOK: 85 :END: 86 * CANCELLED 87:LOGBOOK: 88:END: 89 * 90 * 91 * 92 * 93 * 94 *** INPROGRESS 95 :LOGBOOK: 96 :END: 97 * 98 * 99 * DONE 100:LOGBOOK: 101:END: 102 *** INPROGRESS 103 :LOGBOOK: 104 :END: 105 *** CANCELLED 106 :LOGBOOK: 107 :END: 108 *** INPROGRESS 109 :LOGBOOK: 110 :END: 111 * 112 * 113 * 114 * 115 *** INPROGRESS 116 :LOGBOOK: 117 :END: 118 * 119 *** 120 *** 121 *** 122 *** 123 *** 124 * 125 * 126 * 127 * 128 *** DONE 129 :LOGBOOK: 130 :END: 131 * 132 * 133 *** 134 *** 135 * 136 *** 137 * 138:PROPERTIES: 139:END: 140 *** 141 *** 142 *** 143 *** 144 :PROPERTIES: 145 :END: 146 *** 147:PROPERTIES: 148:END: 149 *** 150 * 151:PROPERTIES: 152:END: 153 * 154 * DONE 155 :LOGBOOK: 156 :END: 157 * 158:PROPERTIES: 159:END: 160 *** DONE 161 :LOGBOOK: 162 :END: 163 :PROPERTIES: 164 :END: 165 *** DONE 166 :LOGBOOK: 167 :END: 168 *** DONE 169 :LOGBOOK: 170 :END: 171 *** DONE 172 :LOGBOOK: 173 :END: 174 * 175 * 176 *** DONE 177 :LOGBOOK: 178 :END: 179 *** DONE 180 :LOGBOOK: 181 :END: 182 *** DONE 183 :LOGBOOK: 184 :END: 185 * 186 *** DONE 187 :LOGBOOK: 188 :END: 189 :PROPERTIES: 190 :END: 191 *** DONE 192 :LOGBOOK: 193 :END: 194 *** D
Re: [O] Citation syntax: a revised proposal
Richard Lawrence writes:
> Agreed. I'd like to see an implementation of a parser for the
> [cite:...] part of the syntax as a first step. If we can get that far,
> I'd guess that extending the parser to include either a subtype label or
> {:key val ...} syntax will not be too difficult to do.
I'll do it by the end of the week.
Regards,
Re: [O] org-agenda - how to move columns
Hi Yuri, thanks for hint. It works perfectly. d. Yuri Niyazov writes: > look into org-agenda-prefix-format. However, you can also change the > category of your org files by putting > > #+CATEGORY: MYCAT > > at the very top of your org files, and that decouples the category > (the first column in agenda) from the filename. > > On Mon, Feb 23, 2015 at 11:59 AM, David Belohrad wrote: >> Dear All, >> >> I'm using quite long filenames for my org files >> (e.g. emails_sent-pcbe13433.org). I get into troubles when constructing >> an agenda as there is not enough space between the first filename >> column and second time column. Is there any way how to adjust the widths >> of the columns in the agenda? >> >> many thanks >> .d. >> >>
[O] Emacs bookmark: org-capture-last-stored
This feature has apparently crept into emacs and orgmode within the last year or so, and I've come to rely on it. I don't remember anything I may have done to make this happen, but now I can have a persistent record of my last capture. Wow! Love it. Can this feature be tweaked to list, say, the last five captures, or ten? Also, the bookmark list only shows the filename where the most recent capture was stored: is it possible to redesign this, so the heading is listed? Still loving org-capture. But except for a number of specialized captures I have been using one capture type and used tags for later sorting. Examples of my more complex usages are (1) a table insertion of temperature and humidity readings; (2) in the moment captures of lexical items when I learn them, with filling of various (band format) categories such as "scientific name" or "english common name" as they are being captured; appointments or deadlines); (3) song lyrics or tablature from the clipboard, captured into a specific file and heading; (4) specific project notes as they occur to me. So my usage is diverse enough that a list of several of the last captures, especially automatically through the bookmark facility of Emacs, would be useful. Thank you for any ideas. Alan Davis
Re: [O] minimal config for bug testing/reporting
Subhan Michael Tindall writes: > I’ve run across what I believe to be a couple of bugs in the use of sticky > agendas. > > I’d like to report them, but I really don’t have the time to rebuild a > functional org-mode .emacs file with minimal configuration. > > Is there one floating around out there I can use that someone can point me at? > There have been many examples on the ML (e.g. http://thread.gmane.org/gmane.emacs.orgmode/80179/focus=80213) It will need a bit of tweaking to accommodate your environment. Nick
Re: [O] minimal config for bug testing/reporting
On Wed, Feb 25, 2015 at 9:28 AM, Subhan Michael Tindall wrote: > Unfortunately gmane is blocked by my company firewall How about the same thread on the org-mode mailing list archives? https://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg0.html
[O] minimal config for bug testing/reporting
I've run across what I believe to be a couple of bugs in the use of sticky agendas. I'd like to report them, but I really don't have the time to rebuild a functional org-mode .emacs file with minimal configuration. Is there one floating around out there I can use that someone can point me at? 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] Bug: org-mouse.el breaks footnote jumping (Reference to definition doesn't work) [8.2.10 (8.2.10-33-g880a2b-elpaplus @ /home/lufimtse/.emacs.d/elpa/org-plus-contrib-20150216/)]
Thank you for testing. Perhaps I could compile the latest development version and see if it occurs there for me. (as currently I'm using 24.4.1 from Fedora 21 repo). I'll try it out and let you know. Leo Ufimtsev | Intern Software Engineer @ Eclipse Team - Original Message - From: "Nicolas Goaziou" To: "Leo Ufimtsev" Cc: emacs-orgmode@gnu.org Sent: Tuesday, February 24, 2015 3:05:07 PM Subject: Re: [O] Bug: org-mouse.el breaks footnote jumping (Reference to definition doesn't work) [8.2.10 (8.2.10-33-g880a2b-elpaplus@ /home/lufimtse/.emacs.d/elpa/org-plus-contrib-20150216/)] Hello, Leo Ufimtsev writes: > I define a footnote via : C-c C-x f as described in the > [manual][1]. > Then I have something like: > > - [ ] Leo once said [fn:1] (reference) > .. > .. > .. > * Footnotes > [fn:1] To make the world a better place, one should use Emacs. > (definition) [fn:1] needs to be at column 0 for a definition. > > I have org-mouse enabled with all org-Mouse-Features > > Now clicking on the definition `[fn:1] To make ..` jumps back to the > reference. > But clicking on the reference doesn't jump me to the definition. > > This works if org-mouse is disabled. I cannot reproduce it on development version. Clicking on the definition jumps me to the reference. Regards, -- Nicolas Goaziou
Re: [O] [ox-odt, bug] math in caption
Rasmus writes: > Hi, > > Consider > > * test > > #+CAPTION: $a$ ain't a \(a\) > | a | > > Expected output is that either $a$ or \(a\) or both are turned into math. > Currently none are. I guess this is at the heart of the problem * test #+CAPTION: $a$ ain't a \(a\) | a | #+BEGIN_SRC emacs-lisp (org-element-map (org-element-parse-buffer) '(latex-fragment latex-environment) 'identity) #+END_SRC #+RESULTS: nil Cf. org-odt--translate-latex-fragments. But I don't know... —Rasmus -- If you can mix business and politics wonderful things can happen!
[O] [ox-odt, bug] math in caption
Hi, Consider * test #+CAPTION: $a$ ain't a \(a\) | a | Expected output is that either $a$ or \(a\) or both are turned into math. Currently none are. —Rasmus -- You people at the NSA are becoming my new best friends!
Re: [O] Citation syntax: a revised proposal
Hi Richard,
2015ko otsailak 20an, Richard Lawrence-ek idatzi zuen:
> OK. I don't anticipate needing {:key val} myself anytime soon; I was
> just trying to future-proof the syntax, and I don't want to lobby for it
> if you feel strongly that this is problematic.
>
> If there are others (John? Aaron? Samuel?) who think they really need
> the {:key val} syntax *over and above* a subtype designation, please
> speak up!
Speaking for myself, I think the discussion so far has revealed a
number of “advanced” uses of citations, such as possessive citations,
citations as footnotes, the insertion of only author/year/etc., ...
At least for academic publishing, citations are pretty demanding and
there isn’t much room for “close enough;” a paper’s citations either
conform to a particular style guide or they don’t.
I think these various applications of citations, and others not yet
mentioned or thought of, are best represented as binary switches. Many
of these distinctions will factor well into independent implementations.
For example, a citation that is :footnote t can (probably) be generated
by taking the citation, whatever it is, and wrapping it in
\footnote{...}. (For the latex case; other backends will have different
specifics but the idea is the same.) If this is implemented in terms of
subtypes, it will lead to an explosion of 2^n subtypes being necessary.
Of course, not all 2^n combinations will be realized (I don’t think it
makes sense for a citation to be both possessive and a footnote, for
example). Ultimately, it’s an empirical question how well different
types of citation factor, and how many of the combinations make sense or
are ever realized.
Nicolas has given reasons why the inline attr syntax is needed
independently. I think no-subtype citations + inline attr is a superset
of with-subtype citations. I’d rather see the superset be implemented.
Subtypes would constrain the expressivity of citations and lead to
more fragile implementations. Since we’re designing the syntax from
scratch, I would like to avoid that.
However, the most important thing is to implement something. The
semipermanent beta status of master allows a period of experimentation
with a citation syntax before something is made official in a release.
Aaron
PS A note on implementation: I envision a sort of pattern matching on
key-value combinations. Something like:
(((:possessive t :footnote t) (error "wtf"))
;; the generated citation command will be inserted at the %s
((:footnote t) (wrap "\footnote{%s}"))
;; slightly artificial example to illustrate pattern matching with binding
((:color _c) (wrap (format "\color{%s}{%%s}" _c)))
((:possessive t) (cite "\citeposs{%s}" ...))
;; cite provides a list of four format strings for the
;; (non-)capitalized (non-)parenthesized
;; variants encoded in the citation type
(default (cite "\cite{%s}" "\parencite{%s}" "\Cite{%s}" "\Parencite{%s}")))
Where the list of attributes is pattern-matched, and the first matching
cite command is composed with all matching wrap commands. I’ve just
shown one-place format strings for the cite key, but a full
implementation would have to handle pre- and post-note. It would
probably also need to handle multicites as a fifth type (or set of 4
types). Though it’s worth considering whether the latex \multicite
family of commands provides anything above and beyond a series of
sequential \cite’s. It might be possible to handle multicites by just
using elisp to concatenate individual citation commands, and not letting
them vary by backend.
The specifics of whether cite and wrap are sufficient primitives needs
to be decided on. Probably we need to allow functions not just format
strings, for the benefit of non-latex backends where the citation needs
to be formatted by emacs. Then cite and wrap would just be predefined
shortcuts, with the ability to drop into full elisp for more complicated
cases.
A small version of the 2^n problem is already visible: the 4 types of
citation necessitate providing 4 strings/functions for the default case,
and also for the possessive case (though I think this is unavoidable
under any implementation).
This is a very rough sketch, but I hope it helps stimulate thinking.
There’s already a pattern matching library in emacs (pcase.el), though
it would need to be extended for plist pattern matching.
--
Aaron Ecay
Re: [O] [PATCH] was Re: [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type argument: listp, t
"Charles C. Berry" writes: > BTW, the string produced when a list cannot be rendered as a table ought > to be removable. > > The patch makes such strings removable. i.e. > > #+BEGIN_SRC emacs-lisp > org-babel-load-languages > #+END_SRC > > will have the ": " prefix or #+begin/end_example delimiters to allow later > removal like this: > > #+RESULTS: > : ((R . t) (latex . t) ... (sql) ... Indeed. I applied a similar patch in 1493151b3fa37496dda12ecbcfc94501ceeafd81. Thank you. Regards,
Re: [O] [RFC] Table's documentation
Hi, I will try to make a patch. Thierry Le 25/02/2015 14:11, Nicolas Goaziou a écrit : Hello, "POSTMASTER @THIERRY-PELLE.EU" writes: reading the 8.3beta manual, I note that *#+NAME: *and *#+CAPTION:* were not "clearly" introduced in the Chapter on tables. (the first in "Remote References" the last in "Images and Tables"). I wonder if it is a good a idea to introduce them in the Chapter or tables (just befor "The Orgtbl minor mode"), refering "Remote References" and "Images and Tables". What do you suggest instead? Regards,
Re: [O] [RFC] Table's documentation
Hello, "POSTMASTER @THIERRY-PELLE.EU" writes: >reading the 8.3beta manual, I note that *#+NAME: *and *#+CAPTION:* > were not "clearly" introduced in the Chapter on tables. (the first in > "Remote References" the last in "Images and Tables"). >I wonder if it is a good a idea to introduce them in the Chapter or > tables (just befor "The Orgtbl minor mode"), refering "Remote > References" and "Images and Tables". What do you suggest instead? Regards, -- Nicolas Goaziou
Re: [O] Here is a patch I want to add to org.el……
Hello, writes: > But how to do it？ Just send it to the list, using "git format-patch" and a proper commit message. See http://orgmode.org/worg/org-contribute.html for more information. > Besides， I‘m glad to view your opinions，so here comes the codes： > > The place：(defun org-ctrl-c-ctrl-c the first (cond > > add： > > (cond >((overlayp (car (overlays-at (point (let ((overlay (car (overlays-at > (point) > (if (overlayp overlay) > (delete-overlay overlay) > ))) > > > so that I won’t make all overlays disappear at only once “C-c C-c” Would you mind explaining what problem you want to solve? Regards, -- Nicolas Goaziou
[O] (feature request) HTML export: include or exclude (filter) content with on todos and tags
Feature request... Post-HTML export, I'd like to be able to include or exclude (filter) content on todos and tags. I could probably roughly hack my way to a solution using a big JQuery plugin and filtering on one of these class attributes. ACTIVE Career so far… work Can I please request a native JS filtering for HTML output? It would be really cool. Thanks John
Re: [O] 8.3 git head new math $ behavior
On Tuesday, 24 Feb 2015 at 18:53, Rasmus wrote:
> \(·\) Should work unambiguously.
And, for the OP, if you are like me and have $...$ burned into your
autonomic system, the following snippet of code is quite useful:
#+begin_src emacs-lisp :tangle "esf-org.el"
;; from Nicolas Richard
;; Date: Fri, 8 Mar 2013 16:23:02 +0100
;; Message-ID: <87vc913oh5@yahoo.fr>
(defun yf/org-electric-dollar nil
"When called once, insert \\(\\) and leave point in between.
When called twice, replace the previously inserted \\(\\) by one $."
(interactive)
(if (and (looking-at ")") (looking-back "("))
(progn (delete-char 2)
(delete-char -2)
(insert "$"))
(insert "\\(\\)")
(backward-char 2)))
(define-key org-mode-map (kbd "$") 'yf/org-electric-dollar)
#+end_src
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-820-gd92ef9
