"Bruce D'Arcus" writes:
> On Sun, Nov 28, 2021 at 12:19 PM Bruce D'Arcus wrote:
>>
>> On Sun, Nov 28, 2021, 12:04 PM Rasmus wrote:
>>
>
>>> However, I think it is currently too aggressive in overwriting styles.
>>>
>>> Could it perhaps accept any style that is given in
>>>
Hello,
Rasmus writes:
> I have noticed that smart quotes are not picked up for “long” languages,
> like “en-gb”, since smart quotes are defined for “short” languages, like
> “en”, in org-export-smart-quotes-alist.
>
> The attached patch is an attempt at remedying this. Not sure if it is the
>
Hi Org community,
Some questions for those of you on Emacs 27 and 28:
Does M-j in an org-mode buffer do what you expect?
Does it throw an error?
What function is M-j bound to in Org?
Backstory:
I have long been on Emacs 26.3 (in Debian stable) but recently decided
to try a newer Emacs from GNU
I'd like to expand the docstring of command `org-agenda-filter-by-tag`
to document the Elisp equivalent of interactive prefix arguments. By
trial and error and guesswork I determined that I could emulate `C-u
C-u` by passing `'(16)` as the second argument
(`strip-or-accumulate`). I'd like to add
Peter Williams writes:
> This is my first time sending mail to the list so let me know if I
> breach any convention.
> ...
> # Cause the Warning
> S R Ξ A S2 X こ T 漢字 Д Ԋ ಱ Ѷ
> # No Problems (= R= is single use)
> 힡 ℤ / s S R nA 漢字 2S _W /W s こ 2 @ _
Welcome and thank you very much for the
Richard,
i also see an error message when entering M-j running:
: emacs -Q foo.org
cheers, Greg
Org mode version 9.5 (9.5-gced2b3 @ /home/minshall/.emacs.d/straight/build/org/)
GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.27,
cairo version 1.17.4) of 2021-03-26
On Sun, Nov 28, 2021 at 12:19 PM Bruce D'Arcus wrote:
>
> On Sun, Nov 28, 2021, 12:04 PM Rasmus wrote:
>
>> However, I think it is currently too aggressive in overwriting styles.
>>
>> Could it perhaps accept any style that is given in
>> ‘org-cite-biblatex-options’ / ‘org-latex-packages-alist’
> Richard Lawrence writes:
> Hi Org community, Some questions for those of you on Emacs 27 and
> 28:
> Does M-j in an org-mode buffer do what you expect? Does it throw
> an error? What function is M-j bound to in Org?
> Backstory:
> I have long been on Emacs 26.3
Hi,
If you want to insert a new element in the list after a particular
element, you could do :
#+begin_src emacs-lisp
(let ((bk (cdr (member '("Agenda Views etc") org-speed-commands
(setf (cdr (member '("Agenda Views etc") org-speed-commands))
(cons '("@" .
Hi,
Thanks for providing ox-biblatex.
It works very well and has replaced my local hacks for LaTeX
bibliographies.
However, I think it is currently too aggressive in overwriting styles.
Could it perhaps accept any style that is given in
‘org-cite-biblatex-options’ / ‘org-latex-packages-alist’
On Sun, Nov 28, 2021, 12:04 PM Rasmus wrote:
However, I think it is currently too aggressive in overwriting styles.
>
> Could it perhaps accept any style that is given in
> ‘org-cite-biblatex-options’ / ‘org-latex-packages-alist’ and only
> overwrite it if another style is explicitly specified
Hi,
I have noticed that smart quotes are not picked up for “long” languages,
like “en-gb”, since smart quotes are defined for “short” languages, like
“en”, in org-export-smart-quotes-alist.
The attached patch is an attempt at remedying this. Not sure if it is the
best fix, though...
Test file:
Hi there,
Congrats on oc.el!
I have had a chance to try it a bit and it is really nice to work with!
One frustration with oc-csl.el is that is does not like relative dirs,
which I guess is fine overall as one would probably store styles
centrally, somewhere, similarly to LaTeX.
However, one
On Sun, Nov 28, 2021, 11:25 AM Rasmus wrote:
> One frustration with oc-csl.el is that is does not like relative dirs,
> which I guess is fine overall as one would probably store styles
> centrally, somewhere, similarly to LaTeX.
>
> However, one niece that would seem useful is to simply dump
This is my first time sending mail to the list so let me know if I
breach any convention.
I seem to be one of many people who have been having issues with
org-element--cache recently. I have been getting the messages quite
regularly in many different cases, but I finally pinpointed one of the
Hi there,
When I try to export documents asynchronously with ox-latex, I always get
a bug in the “org-export-processFOO” files. The last sexp is always something
like this:
(funcall '#
"test.tex")
where the “#” and “’” are mixed around. This happens even with a very
simple
Hi,
I wonder if oc-biblatex should support loading biblatex-derived libraries,
e.g. biblatex-chicago?
There’s a quite a few of these libraries:
$ tlmgr search --global "biblatex-" | wc -l
66
(This is somewhat overestimating the true number of “biblatex-*”
packages).
These libraries
Hello,
Rasmus writes:
> However, I think it is currently too aggressive in overwriting styles.
Ah?
> Could it perhaps accept any style that is given in
> ‘org-cite-biblatex-options’ / ‘org-latex-packages-alist’ and only
> overwrite it if another style is explicitly specified in the file to be
I have just spent an hour trying to figure out what's going on with ELPA,
GNU ELPA, NONGNU ELPA packages. I am lost.
A plethora of methods exist for installing org-mode and other packages; it
is unnecessary to list them, even if I could.
I've been using Emacs and Org-mode for many years. I am
Colin Baxter writes:
> I confirm that it also appears broken to me in emacs-27.2, with the same
> error as you found. I have never noticed it before, possibly because I
> use C-j rather than M-j.
Thanks for confirming. Do you know what the difference between C-j and
M-j is "supposed" to be?
Is there any reason not to autoload the processors?
Bruce
Hello,
"Bruce D'Arcus" writes:
> Is there any reason not to autoload the processors?
I am not sure about what you mean. Could you elaborate?
Regards,
--
Nicolas Goaziou
Richard Lawrence writes:
> Colin Baxter writes:
>
>> I confirm that it also appears broken to me in emacs-27.2, with the same
>> error as you found. I have never noticed it before, possibly because I
>> use C-j rather than M-j.
>
> Thanks for confirming. Do you know what the difference
Agree with Joost. If I remember correctly, the "down" part of markdown was
meant as a play on words to indicate that, unlike a proper markup language,
markdown has a direction and a value system but no defined standard. Since
org is definitely not that why must the waters? Just go for clarity.
On
On Sun, Nov 28, 2021 at 4:34 PM Jean-Christophe Helary
wrote:
>
> Considering the total incompatibility between markdown and org-mode it does
> not seem to me that ’orgdown’ is a useful name. It will only confuse people
> and generate useless comments and counter-comments wherever org-mode
> On Nov 29, 2021, at 7:57, Tom Gillespie wrote:
>
> PS Another brainstormed name: Orgsyn?
Org Agnostic Syntax Modules → OrgASM
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
> On Nov 28, 2021, at 6:22 PM, Jim Porter wrote:
>
> On 11/28/2021 11:46 AM, Karl Voit wrote:
>> At this year's EmascsConf, I had a 12 minute video where I explain why
>> we do need a different name for the syntax of Org-mode in contrast to
>> the Elisp implementation of GNU/Emacs Org-mode.
>>
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> When I try to export documents asynchronously with ox-latex, I always get
>> a bug in the “org-export-processFOO” files. The last sexp is always
>> something like this:
>>
>> (funcall '#
>> "test.tex")
>>
>> where the “#” and “’”
Hi Org-mode community,
At this year's EmascsConf, I had a 12 minute video where I explain why
we do need a different name for the syntax of Org-mode in contrast to
the Elisp implementation of GNU/Emacs Org-mode.
I would like you to read my rationale and motivate you to use the term
"Orgdown" for
Hello,
David Masterson writes:
> Has the format for timestamps covering (say) a few hours changed? The
> following is still possible with "C-c .", but (I think) it is not
> documented in the Org-Mode manual:
>
> <2021-11-27 Sat 10:30-12:30>
>
> This seems to be the new standard:
>
"Alan E. Davis" writes:
> I have just spent an hour trying to figure out what's going on with ELPA, GNU
> ELPA, NONGNU ELPA packages. I am lost.
>
> A plethora of methods exist for installing org-mode and other packages; it is
> unnecessary to list them, even if I could.
>
> I've been using
> I believe (IMHO) that it does not make much sense to separately name the
> Org Mode syntax (as a markup language). That would only generate
> confusion among users.
This is unfortunately not the case. Conflating Org mode which is an Emacs
major mode with Org syntax is a major communication
Max Nikulin writes:
> I am confused. I can not figure out how to create the following as HTML
> export result:
>
>
>
> Attempt to add quotes leads to and does not prevent ":width" to
> become another attribute.
>
>#+attr_html: :alt An image without :width 600 attribute
>
Hi,
I believe (IMHO) that it does not make much sense to separately name the
Org Mode syntax (as a markup language). That would only generate
confusion among users. Furthermore, 'Org Mode', as a whole, is already a
sufficiently recognized and popular name, even outside the GNU Emacs
community. A
Hello,
Rasmus writes:
> When I try to export documents asynchronously with ox-latex, I always get
> a bug in the “org-export-processFOO” files. The last sexp is always something
> like this:
>
> (funcall '#
> "test.tex")
>
> where the “#” and “’” are mixed around. This happens even with
Considering the total incompatibility between markdown and org-mode it does not
seem to me that ’orgdown’ is a useful name. It will only confuse people and
generate useless comments and counter-comments wherever org-mode syntax is
mentioned.
Org-mode and its syntax bring users functions that
I had jokingly suggested "orgup" to have a more positive feeling (up
instead of down) than markdown. I'm not sure orgdown will be any more
confusing than some other name. It could imply a version of the org
syntax that uses markdown surface syntax, but it seems that that would
probably be called
Karl Voit writes:
> Hi Org-mode community,
>
> At this year's EmascsConf, I had a 12 minute video where I explain why
> we do need a different name for the syntax of Org-mode in contrast to
> the Elisp implementation of GNU/Emacs Org-mode.
>
> I would like you to read my rationale and motivate
On Sun, Nov 28 2021, Tom Gillespie wrote:
> PS Another brainstormed name: Orgsyn?
Why not just use the term "Org markup"? It's descriptive and should be
understandable to people familiar with the concept of markup languages.
--
Joost Kremers
Life has its moments
On 11/28/2021 11:46 AM, Karl Voit wrote:
At this year's EmascsConf, I had a 12 minute video where I explain why
we do need a different name for the syntax of Org-mode in contrast to
the Elisp implementation of GNU/Emacs Org-mode.
I would like you to read my rationale and motivate you to use the
On Saturday, 6 November 2021 10:10:55 CET Victor A. Stoichita wrote:
> Greetings to all,
>
> Reading the manual about setting glopal/per-file tags [1], I wonder if
> it is possible to use org-tag-persistent-alist AND per-file
> dynamic tags.
I use footnote 53 from
On 2021-11-28, at 23:25, Juan Manuel Macías wrote:
> Hi,
>
> [...] For example: there is TeX (the typographic engine) and TeX
> (the programming language for that engine). And there has never been any
> conflict.
Quite the contrary. The amount of confusion between TeX (engine)/TeX
Or OrgMark. Simple, please no levels to show the amount of adherence to the
spec. OrgMark would symbolize the "markings" or syntax of Org-mode, and not
be close enough to Mark(down) to where people would think, like I did, that
this was Org-mode power given to a subset of Markdown to help, say,
Hello,
In an org-mode buffer, I have the following:
[[https://first/-/url/][pre]] text [[https://second-url/?][post]]
The “pre” and “text” words appear (wrongly) in italics, as you can see in
the attached screenshot. This misbehavior is certainly related to the
presence of the characters
Juan Manuel Macías writes:
> Joost Kremers writes:
>
>> Why not just use the term "Org markup"? It's descriptive and should be
>> understandable to people familiar with the concept of markup languages.
>
> This. 'Org markup language' and 'Org Syntax' are obvious and natural
> terms that can
Joost Kremers writes:
> Why not just use the term "Org markup"? It's descriptive and should be
> understandable to people familiar with the concept of markup languages.
This. 'Org markup language' and 'Org Syntax' are obvious and natural
terms that can easily be inferred from the Org manual.
Hi Matt,
> I also still don’t really like the behavior
> here. I don’t think it makes sense to interpret a width as 120% if we
> have something like
>
> #+attr_latex: :width 1.2
What would be a more sensible interpretation in your mind? The “true” value
depends on the number of columns, and
Hi Tim,
> I’m wondering if this could be a problem when exporting to latex if the
>underlying latex process encounters errors and is waiting for user input before
>it can continue (which happens if there are problems in the tex source latex is
>trying to process)?
>
> It might be worth checking
48 matches
Mail list logo
