On May 28, 2021, at 11:41 PM, Ihor Radchenko wrote:
>
> Richard Stanton writes:
>> I currently load org using straight.el as follows:
>> ...
>> (use-package org-contrib
>> :after org
>> ...
>> (use-package org
>> :after (jupyter)
>
> I suspect that something else is pulling built-in org versi
Nicolas Goaziou writes:
> By default, no export processor is selected. All citations are
> removed from output, and print_bibliography keywords, ignored.
As I'm coming from LaTeX and have been bitten more than once by
missing citations in the output (which is solved far better today by
biblatex)
Tom Gillespie writes:
> Hi David,
> Laundry produces a full s-expression representation of the org
> parse tree (though it is still evolving). I haven't added a pass that
> converts it to some Racket internal representation (probably will be
> structs). If you get it installed and put #lang o
Nathaniel W Griswold writes:
> Would a patch for this be welcome? Does anyone have any suggestions or ideas?
> I was thinking it should just respect current value of
> `org-id-link-to-org-use-id` but maybe there should be something more specific?
Sounds useful to me. Ideally, it would be even b
Org mode version: 9.4.6
... but the problem is older:
Reproduce:
1. Open org-agenda
2. Open a task from the agenda in the other buffer (i.e. the org file)
3. In the org file, move the cursor away from the task's headline
4. Focus the same task in the org-agenda again
5. Press C-c C-q (org-agenda
On Fri, May 28, 2021 at 4:31 PM András Simonyi wrote:
> Maybe instead of a full alist mapping backends to citation processors
> we could have only options to declare a separate processor for
> latex-based backends and another for non-latex ones?
This would go a long way, and is probably all that
David Masterson writes:
> Testing the usefulness of extensions to the grammar before they're added
> to the grammar..?
For simple cases, there is org-element-update-syntax. Otherwise, you
will probably better use the usual patch/new feature workflow and modify
the parsers directly.
Best,
Ihor
On Sat, May 29, 2021 at 3:51 AM Stefan Nobis wrote:
>
> Nicolas Goaziou writes:
>
> > By default, no export processor is selected. All citations are
> > removed from output, and print_bibliography keywords, ignored.
>
> As I'm coming from LaTeX and have been bitten more than once by
> missing cit
Hello Charles & William,
Berry, Charles writes:
> data.frame($data) is not valid R syntax. If you are new to R doing some
> tutorials will help.
>
> I suggest you use C-c C-v C-v (org-babel-expand-src-block) to see what the R
> code is and debug the result given in the the *Org Babel Preview...
Nicolas, András,
I wanted to pull this example out from oc-biblatex for consideration in oc-csl:
On Tue, May 18, 2021 at 11:45 AM Nicolas Goaziou wrote:
> Bibliography is printed using "\printbibliography" command. Additional
> options may be passed to it through a property list attached to th
Hello,
"Bruce D'Arcus" writes:
>> Bibliography is printed using "\printbibliography" command. Additional
>> options may be passed to it through a property list attached to the
>> "print_bibliography" keyword. E.g.,
>>
>>#+print_bibliography: :section 2 :heading subbibliography
> I don't b
On Sat, May 29, 2021 at 11:15 AM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> >> Bibliography is printed using "\printbibliography" command. Additional
> >> options may be passed to it through a property list attached to the
> >> "print_bibliography" keyword. E.g.,
> >>
> >
Hello,
"Bruce D'Arcus" writes:
> On Fri, May 28, 2021 at 4:31 PM András Simonyi
> wrote:
>
>> Maybe instead of a full alist mapping backends to citation processors
>> we could have only options to declare a separate processor for
>> latex-based backends and another for non-latex ones?
>
> This
"Bruce D'Arcus" writes:
> So two duplicate lists.
>
> Does that clarify?
Indeed, thanks.
> The other common case I am familiar with is a bibliography per section
> of a document.
>
> It may not be practical to do anything other than current behavior,
> but I was hoping some biblatex experts mig
"Bruce D'Arcus" writes:
> Right now, citeproc-el, and hence also oc-csl, only supports the "bare"
> variant.
>
> Would it be feasible, and make sense, to fall back all "bare" variants
> to "bare" for now?
>
> So this:
>
> [cite//bare-caps:@latexcompanion]
>
> ... would render as:
>
> Doe 2019
W
On Sat, May 29, 2021 at 12:34 PM Nicolas Goaziou wrote:
>
> "Bruce D'Arcus" writes:
>
> > Right now, citeproc-el, and hence also oc-csl, only supports the "bare"
> > variant.
> >
> > Would it be feasible, and make sense, to fall back all "bare" variants
> > to "bare" for now?
> >
> > So this:
>
On Sat, May 29, 2021 at 1:25 PM Bruce D'Arcus wrote:
>
> On Sat, May 29, 2021 at 12:34 PM Nicolas Goaziou
> wrote:
> > We dropped variant inheritance some time ago already, when the suggested
> > syntax was style/variant/subvariant... Now, "bare" and "bare-caps" are
> > totally different from O
HTML export wraps headlines in anchor tags with IDs, so that they can be
linked by suffixing #[anchor-tag-ID] to the URL.
HTML export used to use anchor IDs like "sec-2" for the second headline,
but at some point it switched to generated IDs like "org7ffb324", which
change on every re-export.
T
Hi Ihor,
Yes, happy to put my test cases into the org element cases and
visa versa. My long term plan is to come up with a set of test cases
that are unambiguous and potentially ambiguous so that we can
determine the expected behavior in those cases, so this is a great
first step. Best,
Tom
Hello,
sba...@catern.com writes:
> HTML export wraps headlines in anchor tags with IDs, so that they can be
> linked by suffixing #[anchor-tag-ID] to the URL.
>
> HTML export used to use anchor IDs like "sec-2" for the second headline,
> but at some point it switched to generated IDs like "org7ff
Nicolas Goaziou writes:
> No, for public links, CUSTOM_ID is the only sane way to handle this.
> Even "sec-2" could betray you if you slightly modify the document.
Hi Nicolas,
On this, would you have any interested in going back to that thread
about IDs generated based on the headings? IIRC i
"Bruce D'Arcus" writes:
> Oh wait, I just realized citeproc-el already has a parameter for
> "caps" (which I hadn't realized).
>
> - "bare" -> "suppress-affixes" parameter
> - "caps" -> "capitalize-first"
>
> Right?
>
> So that would allows support for:
>
> - "bare"
> - "caps"
> - "bare-caps"
Co
Hello,
Juan Manuel Macías writes:
> I'm sorry, it's my fault. It's already fixed. I think the patch attached
> here should apply well...
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Markus Huber writes:
> lisp/ox-latex.el (`org-latex--make-option-string'): If `value' of a `pair'
> from `options' contains a bracket
> the whole `value' is surrounded by braces.
>
> In case of LaTeX export using listings the dialect of a language (e.g.
> [LaTeX]TeX) is surrounded by br
Hello,
Greg Minshall writes:
> hi. neither =make clean= nor =make cleanall= remove the two .texi files
> built (by, e.g., =make info=) in the doc subdirectory. this patch
> removes those files with =make cleanall=. i wasn't sure which to use,
> but it sort of looked like =cleanall= might be t
Hello,
mohsin kaleem writes:
> I've been trying to get async-export setup for the past day and I've
> found it keeps failing due to an unexpected # in the compilation script
> generated by org-export.
>
> After doing a little debugging I found the script contained
> ~(funcall '#
> "foo.tex")~
>
Just wanted to update this thread in that the following DID resolve my issue
with my Yasnippet template which overrides the default " Samuel Banya writes:
> > Do you think that maybe changing the setting you had mentioned before,
> > 'org-src-tab-acts-natively' to false (aka nil or '0' (zero) val
If you insert the format string into a temporary buffer, then the `read'
function will read up to the closing parenthesis and update point
accordingly. That would be a foolproof way to handle all possible Lisp
forms: use a regexp to find the start, and then use `read' to find the end.
Then proceed
Hi,
thanks to Albert for pointing me to pandoc-quotes.lua.
It doesn't take care of apostrophes so I wrote my own very simple pandoc
lua filter:
text = require 'text'
function Str (s)
s.text = pandoc.pipe("sed", {"-e","s/'/’/"}, s.text)
return s
end
Together with pandoc-quotes.lua and "
Timothy writes:
> Nicolas Goaziou writes:
>
>> No, for public links, CUSTOM_ID is the only sane way to handle this.
>> Even "sec-2" could betray you if you slightly modify the document.
>
> Hi Nicolas,
>
> On this, would you have any interested in going back to that thread
> about IDs generate
Ihor Radchenko writes:
> David Masterson writes:
>> Testing the usefulness of extensions to the grammar before they're added
>> to the grammar..?
>
> For simple cases, there is org-element-update-syntax. Otherwise, you
> will probably better use the usual patch/new feature workflow and modify
>
Hi. I continue below:
Em [2021-05-29 sáb 21:53:47-0300], Jorge P. de Morais Neto escreveu:
> I stepped through the code and verified the error is triggered at line
> 1726 on file org-clock.el. This is the form
> (org-back-to-heading t)
> on function `org-clock-remove-empty-clock-drawer'. T
org-log-note-clock-out--bug.el
Description: Elisp to reproduce the bug
Hi. I use Emacs from Guix---package emacs-next installed from Git
master (through --with-branch=emacs-next=master) and updated weekly.
Org is also from Guix: packages emacs-org{,-contrib,-drill,-pdftools}
To reproduce the bu
Ypo writes:
> Hi! Thanks for answering. It was just a thought. Habits appear like this
> (not sure how images can be attached in the mail list):
>
> borrar-1
>
> I thought it would be interesting to have the option to show them like this:
>
> borrar-2
>
> Thanks for your interest
You can do it
Tom Gillespie writes:
> Hi Ihor,
> Yes, happy to put my test cases into the org element cases and
> visa versa.
Patches welcome ;)
Tim Cross writes:
> Timothy writes:
>
>> On this, would you have any interested in going back to that thread
>> about IDs generated based on the headings? IIRC it petered out more that
>> reached a conclusion.
>
> I thought the conclusion was that if you wanted link stability, use
> publish ra
Vladimir Nikishkin writes:
> Would it be possible to, instead, add a small link, with the same href,
> and the visible part of something short, such as (#) or (*) hear the
> headline.
This sounds useful. An example of implementation is
https://tecosaur.github.io/emacs-config/config.html
Timothy
Mauro Aranda writes:
> 5. I expected to get a clean row:
> Here is a table:
> | | |
> | Data1 | Data2 |
>
> but I got:
> Here is a table:
> | | Data2 |
> | Data1 | Data2 |
Confirmed
Eric S Fraga writes:
> When I try this now, with org up to date from git, I get this backtrace:
>
> ,
> | Debugger entered--Lisp error: (error "Invalid duration format: \"3pm\"")
Confirmed
Ihor Radchenko writes:
> Vladimir Nikishkin writes:
>
>> Would it be possible to, instead, add a small link, with the same href,
>> and the visible part of something short, such as (#) or (*) hear the
>> headline.
>
> This sounds useful. An example of implementation is
> https://tecosaur.githu
40 matches
Mail list logo
