Hi,
On 2021-04-20, 15:40 +0200, Nicolas Goaziou wrote:
> Again all this needs to extensively tested, as there are a lot of
> dangers lurking around.
I am attaching my patch which also include my previous suggestion of
including yes-or-no prompt to org-table-import to allow file which don't
Mentioning this again for fresh attention to whoever can push an update: the
online manual is older than the version in the source tree.
I noticed this from the Working with Source Code / Languages section. For
example, the source org-manual.org file says, "Code blocks in dozens of
Hi all,
I originally thought having the timezone in the header of the file would make
things simpler, since it meant all the timestamp would be in the same timezone,
rather than potentially different ones. But it seems that that might not be
inline with how others use their org files.
org
On 4/22/21 4:29 PM, Anthony Carrico wrote:
Practically speaking, the script included by org-mode is in the public
domain, so it could never conflict with whatever license the author
chooses. Therefore, we should remove the LibreJS tag from the
>From 8f86d82b6784d26d8af86de01adcf333ee81148b Mon Sep 17 00:00:00 2001
From: Anthony Carrico
Date: Thu, 22 Apr 2021 17:32:59 -0400
Subject: [PATCH] Org-mode publish avoids inserting script license tag into
target documents
* ox-html.el: In previous versions, org-export included a script
Jean Louis writes:
> * David Masterson [2021-04-20 00:59]:
>> What is the current status of having a BNF (or...?) parser for Org
>> files? In particular, the parser rules that could then be adopted by
>> tools that use Org files on other systems (iPhone, Android, ...)? Given
>> the
Tom Gillespie writes:
> Hi Tim, David, and Gustav,
Hi
> I am fairly certain that with only a few exceptions it is possible
> to specify a context free grammar for org syntax, followed by a second
> pass that deals specifically with markup and a few other forms,
> notably the reassembly of
Gustav Wikström writes:
> You didn't ask me, but since I'm currently here and reading the list I
> might just give 2c to the topic.
Your 2c appreciated. I'm looking to learn.
> My understanding is that a BNF-grammar is virtually impossible for
> Org. The org language is ambiguous and writing
On 4/22/21 5:20 PM, Tim Cross wrote:
Appreciate the intention. Perhaps we need to clarify what exactly we are
licensing here
I'm sorry, I didn't realize that you were missing the context; it is a
tiny
Anthony Carrico writes:
> On 4/20/21 12:55 AM, Tim Cross wrote:
>> The error from libreJS is correct - public domain is not a valid
>> license.
>
> Everyone is licensed to use public domain works (except to obtain a copyright
> on
> them). I think you mean that libreJS is working by design
FYI, I started to implement a function to format the org-cite syntax here:
https://github.com/bdarcus/bibtex-actions/pull/113
When finished, and org-cite merged, I plan to submit it for inclusion
in bibtex-completion.
Bruce
On 4/20/21 12:55 AM, Tim Cross wrote:
The error from libreJS is correct - public domain is not a valid
license.
Everyone is licensed to use public domain works (except to obtain a
copyright on them). I think you mean that libreJS is working by design
when it blocks them, which is apparently
Hi all. Thanks for the note. I took a look at the LibreJS docs to try to
understand the problem. My analysis:
LibreJS is a web filtering plugin. Users are making a decision to block
content which is not explicitly licensed in the LibreJS syntax,
including public domain works marked in that
Hi,
Am 22. April 2021 um 01:34 Uhr +0200 schrieb Nicolas Goaziou:
> A noteworthy difference with the last merge is that I removed the
> opportunity to add some Org syntax (emphasis, sub/superscript…) in
> prefixes or suffixes. It makes the code a bit simpler. Of course, I'm
> open to discussion
Hi,
I recently posted to the help-gnu-emacs mailing list about using the
org-mode package "org-drill" and its long-term viability considering
that it is no longer actively maintained - you can see the thread
[here](https://lists.gnu.org/archive/html/help-gnu-emacs/2021-04/msg00230.html).
The
On Thu, Apr 22, 2021 at 11:36 AM Nicolas Goaziou
wrote:
> Tim Visher writes:
>
> > Thanks for the tip. What I'm thinking more is somehow getting the heading
> > pre-output generation, stripping any characters that `org` would consider
> > special (I'm hoping there's already a function that can
Tim Visher writes:
> Thanks for the tip. What I'm thinking more is somehow getting the heading
> pre-output generation, stripping any characters that `org` would consider
> special (I'm hoping there's already a function that can at least mark
> 'markup' text in a given org string), and _then_
Hi,
On Thu, Apr 22, 2021, at 9:32 PM, Nicolas Goaziou wrote:
> I would say
>
> See also [[*Sparse Trees]].
>
> The ~org-show-context-detail~ variable is mentioned there anyway.
I agree. A new patch for docs is attached.
> > + ancestors-full show current subtree and its direct ancestors
>
On Thu, Apr 22, 2021 at 9:52 AM Nicolas Goaziou
wrote:
> Tim Visher writes:
>
> > Awesome. Do you know whether there's an official way to share this sort
> of
> > behavior between ox backends or is it just creating a function and
> calling
> > it from both places or something?
>
> Do you want
Hello,
Tim Visher writes:
> Awesome. Do you know whether there's an official way to share this sort of
> behavior between ox backends or is it just creating a function and calling
> it from both places or something?
Do you want to remove all markup from some parsed text?
You could define
Hi Nicolas,
Thank you very much for your suggestions.
Nicolas Goaziou writes:
> This change will need to be tested extensively in "test-org-element.el"
> and "test-org-macro.el".
>
> However, as a start, I suggest starting a new thread about a suggested
> change in the syntax, with a clear
Hello,
"Cheong Yiu Fung" writes:
> Subject: [PATCH 2/2] org-manual.org: add hints for visible-only export
Thanks. Some comments follow.
> + particular headings. See also the variable
> + ~org-show-context-detail~ and the command ~org-sparse-tree~.
I would say
See also [[*Sparse
On Thu, Apr 22, 2021 at 9:14 AM Nicolas Goaziou wrote:
> Now, I hope to see some work towards "oc-citeproc.el" (or any other
> processor). We need it to push the limits of "oc.el", e.g., to decide if
> it should provide more tools, or more breadth in its API.
>
> As stated already, I will be
Hello,
"Bruce D'Arcus" writes:
> The haskell citeproc library has this:
>
> "a CiteprocOptions structure (which currently just allows you to set
> whether citations are hyperlinked to the bibliography)"
>
> Would something like that make sense as an optional argument somewhere
> here? Or would
Hello,
Juan Manuel Macías writes:
> I think it's a very interesting idea. I've made this sketch (at least
> as a proof of concept), what do you think of the approach?
I think there are a few things to fix. For example, the separator may
need to be stored in the properties of the macro.
Eli Zaretskii writes:
>> From: Arthur Miller
>> Cc: 47...@debbugs.gnu.org
>> Date: Wed, 21 Apr 2021 22:10:45 +0200
>>
>> >> Because you have font-lock-mode turned on. And JIT font-lock begins
>> >> by wiping out all the text properties.
>> >
>> > I should clarify this, I guess: this is
Bruce D'Arcus writes:
> If point is within the citation brackets, you see the raw syntax, so
> you can edit it.
>
> Once you are outside the brackets, having already inserted the
> citation, you see a preview of the output.
This sounds quite sensible to me. I'd be happy with some sensible
On Wed, Apr 21, 2021 at 10:47 PM Timothy wrote:
> I think what would be ideal, would be if common citation styles could
> define a method which produces a display string, like "Goaziou et al.
> (2021)". If nothing is defined, then no overlay should be produced.
Make sense, but with a caveat:
On Wed, Apr 21, 2021, 7:34 PM Nicolas Goaziou wrote:
> `:export-bibliography'
>
> Function rendering a bibliography. It is called with five arguments: a
> list
> of citations, a list of bibliography files, the style, as a string or
> nil,
> the export back-end, as a
There's a list of languages here [1]. It looks like someone helpfully added
maintainers to the table. You could find languages without a listed
maintainer there and then check the header of the source file [2] to be
sure there's no current maintainer.
[1]
On Wed, Apr 21, 2021 at 9:49 PM Tim Cross wrote:
>
> ian martins writes:
>
> > On Wed, Apr 21, 2021 at 3:45 PM Tim Cross wrote:
> >
> > Responding to essentially just flag you have seen the patch message
> > really only adds noise and may even 'drown out' those responses which
> > add real
I just pushed a patch. Your example works now. (Don't forget to change
stdio.h into ).While waiting for the patch to be released, you
can load this Lisp file:
https://code.orgmode.org/bzg/org-mode/src/maint/lisp/ob-C.el
Cheers
Le 02/04/2021 à 19:40, Richard Sent via General discussions about
32 matches
Mail list logo
