possible with CSL, so I look for another
way to automate this during the export process.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
number. That came a bit by surprise.
So, what is the correct way to target the content of a footnote in a
filter across backends?
Org mode version 9.5 (release_9.5-484-g98588e @
/home/quintus/.emacs.d/org-mode/lisp/)
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Tim Cross writes:
> William Denton writes:
>
>> I noticed org-modern in the list of new packages available:
>>
>> https://github.com/minad/org-modern
>>
>> Worth a look by any Org users, just for the screenshots comparing Org
>> buffers normally and with
>> org-modern. Fine work from Daniel
I'm a happy org-mode user who usually just lurks on the list, but I have some
expertise of note to share on the issue of taking donations and proprietary
Javascript.
I've spent much time over the last 25 years working for and/or helping to run
various non-profit organizations related to FOSS.
Tim Cross writes:
> Is the transient.el included in Emacs 28 the same as the one on GNU
> ELPA? I'm assuming it is, but I have to admit I'm still not 100% clear
> on how Emacs handles the situation where you use a library that is both
> built-in and available in ELPA. Does Emacs use the latest
Today, I found the Org Agenda sorting strategy problem is fixed by commit
"1b675f0ca84d637a3780cf3590308116e232fcfd".
Thanks, TEC
Bastien writes:
> Hi,
>
> stardiviner writes:
>
>> org-agenda-sorting-strategy bug? Cannot list deadline items before scheduled
>> items.
>>
>> With the
I tested this commit, it should auto append a newline character after
~org-agenda-clock-report-header~. Otherwise the header line will in same line
with table first line.
Samim Pezeshki writes:
> Thanks Nicolas for reviewing the changes!
>
> I applied the changes.
> Attached is the updated
Ihor Radchenko writes:
>> I suggest to keep current defaults. Because I have lot of Org files, if
>> changed, I have to do lot of
>> work to adopt files and might get wrong. It's very important.
>
> Org mode does not distinguish the _meaning_ of all keywords regardless
> of their case.
Timothy writes:
> Hi Christopher,
>
>>> Is there a good reason for this?
>>>
>>> At a glance, I’d personally be tempted to make the use case insensitive, and
>>> only use `org-babel-results-keyword’ when inserting, or remove it all
>>> together.
>>
>> Me too, I hope it can be case-insensitive,
Timothy writes:
> Hi Christopher,
>
>> I suggest to keep current defaults. Because I have lot of Org files, if
>> changed, I have to do lot of
>> work to adopt files and might get wrong. It’s very important.
>
> Hmm. Upon inspection I see that some uses of `org-babel-results-keyword' are
>
I suggest to keep current defaults. Because I have lot of Org files, if
changed, I have to do lot of
work to adopt files and might get wrong. It's very important.
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express.
Blog:
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>>> we are entering the territory of Emacs
>>> build-dependent bugs...
>>
>>> My best suggestion then is going to
>>> org-element.el and changing "(version< emacs-
Good idea to add header for clock report table.
Samim Pezeshki writes:
> Hi,
>
> This patch adds a header to the clock report table in the agenda, if
> org-agenda-clock-report-header is set.
>
> Thanks,
> Samim
>
> [4. text/x-patch;
>
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> Here is my reproduce environment:
>>
>> Reproduce test with =emacs -Q=
>>
>> #+begin_src shell :eval no
>> emacs -Q -l ~/.config/emacs/minimal-org-init.el ~/org-persist-test.o
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> I git bisected org-mode source code, and found the commits after
>> "410afd6f374e9" caused org-agenda
>> does not display scheduled and deadline tasks. Also affects org-contacts
I git bisected org-mode source code, and found the commits after
"410afd6f374e9" caused org-agenda
does not display scheduled and deadline tasks. Also affects org-contacts
completion get contacts
email property.
I'm using the latest commit "dc4b2772e".
I use bug-hunter extension to test my
Jack Kamm writes:
> Hi Christopher,
>
>> This might need to mentioned in Org manual and in ob-python.el source
>> code with comment. WDYT?
>
> The main documentation for this is in the Worg page for ob-python, in
> particular see the section "Return values":
>
>
Thanks Jack. Confirmed works. This might need to mentioned in Org manual and in
ob-python.el source
code with comment. WDYT?
Jack Kamm writes:
> For non-session Python blocks, you need to use "return" on the value, as
> if you are in a function.
>
> The following works for me:
>
> #+begin_src
The bellowing python source block ~:results value pp~ does not print pprint
formated result as
expected. I tested with =$ emacs -q= confirmed this problem.
#+begin_src python :results value pp
dic = {'key1': 1, 'b': 2}
dic
#+end_src
#+RESULTS[(2021-12-29 10:51:14)
"Christopher M. Miles" writes:
> [[PGP Signed Part:Undecided]]
>
> The bellowing python source block ~:results value pp~ does not print pprint
> formated result as
> expected. I tested with =$ emacs -q= confirmed this problem.
>
> #+begin_src python :results va
lementing org markup.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
he "horrible
> name" for a change. Thank you for that. ;-)
I enjoy this discussion and am curious about how it continues.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
ly on par with Markdown.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
There is attributes setting above image link to specify image inline preview
size. Like this:
#+begin_src org
,#+ATTR_ORG: :width 500
,#+ATTR_LATEX: :width 5.0in
,#+ATTR_HTML: :width 500px
[[file:kk/88320740_p0.jpg]]
#+end_src
When I put it on beginning of org document, then preview inline
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> I can't reproduce it with clean Emacs config. And my option
>> ~org-adapt-indentation~ is ~nil~. And this
>> error is not raised every time. Just some org buffer and sometimes. Have not
>> no
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> I can't reproduce it with clean Emacs config. And my option
>> ~org-adapt-indentation~ is ~nil~. And this
>> error is not raised every time. Just some org buffer and sometimes. Have not
>> no
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> The bellowing error often raised when I region select multiple headlines
>> which contains properties
>> drawer
>>
>> #+begin_src org
>> |*** headline 1
>> :PROP
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> When I put point on an custom org link:
>>
>> #+begin_src org
>> [[pdf:~/Org/Wiki/Computer Technology/Programming/Programming
>> Languages/Clojure/data/Books/Clojure
>> 经典实例.pd
When I put point on an custom org link:
#+begin_src org
[[pdf:~/Org/Wiki/Computer Technology/Programming/Programming
Languages/Clojure/data/Books/Clojure经典实例.pdf::40++0.00][Clojure经典实例.pdf: Page
40]]
#+end_src
Then press =[M-: (org-element-context) RET]= to get link element properties. I
got
The bellowing error often raised when I region select multiple headlines which
contains properties
drawer
#+begin_src org
|*** headline 1
:PROPERTIES:
:kkk: 2
:END:
,*** headline 2
:PROPERTIES:
:kkk: 3
:END:
|
#+end_src
(Here the ~|~ and ~|~ represent the region select two
Am Freitag, dem 19. November 2021 schrieb Nicolas Goaziou:
> I think a better order for a relative file name would be:
>
> 1. relatively to `org-cite-csl-styles-dir',
> 2. relatively to buffer's default directory,
> 3. failure.
>
> WDYT?
I would be fine with it.
-quin
tion after amending
`org-cite-csl--label-alist' results in the desired result on export.
Thanks!
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
(push '("Kap." . "chapter") org-cite-csl--label-alist)
Interestingly, doing this does not make it work for me, the “Kap.” still
is displays at the beginning.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
-function
'org-latex-format-inlinetask-default-function
org-html-format-drawer-function '(closure
(htmlize-buffer-places
org-html-format-table-no-css
htmlize-css-name-prefix htmlize-output-type
htmlize-output-type
htmlize-css-name-prefix t)
(_name contents) contents)
org-html-format-headline-function 'org-html-format-headline-default-function
)
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
I have following Clojure source block:
#+begin_src clojure
(re-find #"\d+" "I've just finished reading Fahrenheit 451");; => "451"
(re-find #"Bees" "Beads aren't cheap.");; => nil
#+end_src
When I press =[C-c C-c]= to evaluate source block, got error:
When there is no comments behind code
Am Samstag, dem 06. November 2021 schrieb András Simonyi:
> I've pushed a change to citeproc-el which should solve that problem --
> thanks for reporting it.
Thank you again! It works now properly.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> In the source code comment "FIXME" org-agenda always in frontend and popup
>> buffer. I can't generate
>> org-agenda in background then get the buffer content.
>>
>> Does anyb
y actions. I
> save timestamps on changing TODO to DONE, use active timestamps for
> appointments, and I constantly add inactive timestamps while taking
> notes. I use this to justify billing to clients.
>
> I open the agenda, v m to make a monthly view, L for logbook, ] to
> ena
yles-dir' is not nil,
check if it resolves to an existing file; if no such file exists, expand
against `default-directory'. If `org-cite-csl-styles-dir' is nil, expand
against `default-directory'.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutsc
2la@nicolasgoaziou.fr/T/#m04c52902b1b2cb813269cac8088b4de94f0fcf2b
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> Thanks for quick patch, I'm on the latest main. and I pulled your patch. Now
>> it's not infinite
>> looping, but still takes about 3.5 seconds. So I take another profiler
>> profiling
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> Here is the profiler report:
>>
>> CPU:
>>
>> #+begin_example
>> 4003 66% - command-execute
>> 4003 66% - call-interactively
>> 3913 65%
%+ find-coding-systems-region
6 0%if
220 3% + org-persist--get-index
2 0% + valign--maybe-clean-advice
592 9%+ counsel-M-x
1 0%+ previous-line
90 1% + ivy-completing-read
Thanks, confirmed solved.
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> I applied your patch on the latest pulled org-mode source code. Still can't
>> org-fill elements
>> quickly when region select text contains org headlines, properties dr
I applied your patch on the latest pulled org-mode source code. Still can't
org-fill elements
quickly when region select text contains org headlines, properties drawer etc.
If I only fill paragraph, it is fine.
<#secure method=pgpmime mode=sign>
--
[ stardiviner ]
I try to make every
When I press [M-q] on the following org-mode buffer content:
#+begin_src org
,* 绵羊是太阳能农场的优秀管理员
:PROPERTIES:
:SOURCE: 奇客Solidot–传递最新科技情报
:DATE(original): [2021-10-25 Mon 17:28]
:DATE: [2021-10-26 Tue]
:END:
有利于放养家畜和有利于太阳能发电的地方经常重叠。它们都需要平坦、阳光充足，没有高大植被的开阔地。因此
太阳能生产商正越来越多地租用农田运营。
太阳能产量的增加具有环境效益，但
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> Confirmed after change from "28" to "29" solved the problem in your steps.
>>
>> I also tested this change on my current Emacs config. Also confirmed solved
>> the prob
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> My Emacs version (on M1 macOS)
>>
>> GNU Emacs 28.0.60 (build 1, aarch64-apple-darwin20.6.0, NS appkit-2022.60
>> Version 11.6 (Build 20G165)) of 2021-10-20
>>
>> Thanks for
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> I put this scheduled task into a separated org file and clean
>> org-agenda-files variable, and set it
>> to only this new separated org file. Not displayed.
>
> I finally managed reproduce
nciate the two cases:
This is probably a bug.
Org mode version 9.5 (release_9.5-104-g2b1fc6 @
/home/quintus/.emacs.d/org-mode/lisp/)
citeproc.el at 34e66583d95a8d80fb5b9f2960f3382ca0e6d3ab
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> I'm git bisect on the latest git-pulled org-mode. Still located bad commit
>> on this bad commit. Seems
>> commit also introduced other problem.
>
>> #+begin_example
>> 0ef88e2d9
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>> Now I tried your latest push. The errors gone. But org-agenda entries still
>> missing. I checked
>> *Messages* buffer, no error messages, including other error special buffers.
>> no information
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>> Now I tried your latest push. The errors gone. But org-agenda entries still
>> missing. I checked
>> *Messages* buffer, no error messages, including other error special buffers.
>> no information
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> After git bisect, I found the bad commit:
>>
>> #+begin_example
>> 0ef88e2d9 * | bad @ org-agenda.el/org-agenda-get-scheduled: Use cache
>> #+end_example
>>
>> after org-age
After git bisect, I found the bad commit:
#+begin_example
0ef88e2d9 * | bad @ org-agenda.el/org-agenda-get-scheduled: Use cache
#+end_example
after org-agenda generation, lot of entries not displayed. Then I found lot of
errors in =*Messages*= buffer.
#+begin_example
Wrong type argument:
Max Nikulin writes:
> On 20/10/2021 16:58, Christopher M. Miles wrote:
>> Just update the email subject contains [PATCH]
>> "Christopher M. Miles" writes:
>> Mostly Emacs versions under macOS does not have compiled with DBus.
>> Or still don't wo
Just update the email subject contains [PATCH]
"Christopher M. Miles" writes:
> Mostly Emacs versions under macOS does not have compiled with DBus. Or still
> don't work even compiled with DBus even
> macOS installed dbus with homebrew. I'm under this situation and pr
Mostly Emacs versions under macOS does not have compiled with DBus. Or
still don't work even compiled with DBus even macOS installed dbus with
homebrew. I'm under this situation and problem. Spend lot of time have
not solution to solve this problem. So I give up on Emacs DBus support
under macOS
sier when pandoc supports org's new citation syntax?
There's a ticket for this open: https://github.com/jgm/pandoc/issues/7329
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
corresponding ebib entry, I suppose there is a way. In ebib then it
is as easy as pressing “f” to open the PDF referenced in the “file”
field.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
orithm doesn't
> handle some of your examples correctly -- could you open an issue
> about this on the project page? Thanks in advance!
Done: https://github.com/andras-simonyi/citeproc-el/issues/58
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
Das ist ein Test [cite:@saenger2013gsr §§ 12-14].
is correct again:
Saenger, Gesellschaftsrecht, 2. Aufl. (2013), §§ 12-14
This is a little confusing. Maybe an error on my part? Do I need to
signal singular and plural use more explicitely?
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.
is a bug in locales-de-DE.xml,
and I guess Pandoc proves my point here. Please map § to "section"
instead of "paragraph" in org-cite, i.e., do it the way Pandoc does it.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
tsrecht, 2. Aufl. (2013), ¶¶ 12 Rn. 488
As explained, the positioning is now correct. However, instead of the
section § sign it now has two pilcrow signs ¶¶. It should be just one
sign, and it should be a section sign rather than a pilcrow one.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.
being short for "Zeile", i.e. "line" in German).
So this appears to be a problem specifically with the § sign?
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
Am Sonntag, dem 10. Oktober 2021 schrieb Nicolas Goaziou:
> Then, this may be a bug in Citeproc library itself. I suggest to report
> it upstream.
Done: https://github.com/andras-simonyi/citeproc-el/issues/57
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe We
at is,
Das ist ein Test [cite:@saenger2013gsr § 12 Rn. 488].
it yields:
§ Saenger, Gesellschaftsrecht, 2. Aufl. 2013, 12 Rn. 488
Neither is correct; the § should go after the "2013, ".
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Pa
ude from this that org somehow mistreats the locator if it is not
a page number. I used org 9.5 from MELPA and Citeproc.el from commit
34e66583d95a8d80fb5b9f2960f3382ca0e6d3ab.
Is it a bug or (again) my error?
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Websei
Am Freitag, dem 08. Oktober 2021 schrieb Nicolas Goaziou:
> Meanwhile, the `csl' processor is copiously documented in the
> "Commentary" section of the "oc-csl.el" file.
Thanks for the heads-up. Next time I will take a look there as well.
-quintus
--
Di
te-csl-locales-dir' to the repository's directory.
I agree with Bruce that this should be mentioned in the manual,
including a pointer to the aforementioned Git repository, because I
needed to find that one on my own.
Thanks again!
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP:
eature (if so, I
would like to request it), or a user error on my side. Please enlighten
me.
I used org 9.5 from MELPA with citeproc.el from the Git repository at
34e66583d95a8d80fb5b9f2960f3382ca0e6d3ab.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
introduced
un-reimplemented variable ~dir~.
>
> I'll post a new patch with a different approach in a little bit.
>
> On Mon, Oct 4, 2021 at 5:06 PM Christopher M. Miles
> wrote:
>
> Ihor Radchenko writes:
>
> Greg Minshall writes:
>
> i can imagine wantin
Ihor Radchenko writes:
> Greg Minshall writes:
>
>> i can imagine wanting to have input files and
>> output files in separate directories. (for ease in "make clean", if for
>> no other conceptual reason.) (but, probably i don't understand.)
I agree with this thought. We should separate two
om/andras-simonyi/citeproc-el/issues/54>
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
Passau, Deutschland | kont...@guelker.eu| O<
<#secure method=pgpmime mode=sign>
I have following advice code:
#+begin_src emacs-lisp
(defun my/org-add-note--auto-add-tag ()
"Auto add tag 'LOG' when add note log."
(org-back-to-heading)
;; DEBUG: the following code is not executed.
(message "DEBUG")
(require 'seq)
(org-set-tags
but does exist. As an aside,
I hope that pandoc will receive support for org's new citation syntax
soon.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu |For security:
Passau, Germany | kont...@guelker.eu| () Avoid HTML e-mail
European Union | PGP: see homepag
Amazing! Thank you to everyone that contributed. I am looking forward to
start playing with this. :)
Nicolas Goaziou writes:
> Hello,
>
> It took years, but citations are now full part of Org syntax.
>
> Thanks to everyone involved over the time!
>
> Now, it needs to be documented, but that
Am 05. Mai 2021 um 14:27 Uhr -0400 schrieb Bruce D'Arcus:
> Hope that explains.
Sure, thank you! I just wanted to provide some possibly useful input.
I am not to critise these exciting efforts.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu |For security:
Passau, Germ
being said, I never saw such a
construction.
At least, that are the rules I recall from my school time and which I
used ever since with nobody complaining.
I wonder, can the placement of the footnote not just be left to the
author...? I have the impression that something is being
over-engineered h
ot all journals handle it like that,
though. Some do prefer uniform look and glance over the semantic
difference.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu |For security:
Passau, Germany | kont...@guelker.eu| () Avoid HTML e-mail
European Union | PGP: see homepage | /\ http://asciiribbon.org
hard work on this feature.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu |For security:
Passau, Germany | kont...@guelker.eu| () Avoid HTML e-mail
European Union | PGP: see homepage | /\ http://asciiribbon.org
tes
with numbers like “4a” (a footnote inserted at a late stage in the
authoring process between footnotes 4 and 5), which defeats the
lowest-number approach.
For non-footnote-based citations, the “helper function to determine
the footnote containing a citation” should probably return nil.
-qui
th all the potential for name
collisions and the like that that implies. One could avoid such problems by
adding some kind of prefix to the block names in the included file (maybe
"common/" or "xyzzy-"). (Some kind of automatic prefixing on inclusion might be
cool.)
--Kevin M. Stout
tus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu |For security:
Passau, Germany | kont...@guelker.eu| () Avoid HTML e-mail
European Union | PGP: see homepage | /\ http://asciiribbon.org
HI Kyle,
This solved my problems
Thanks,
M
> On Mar 9, 2021, at 11:49 PM, Kyle Meyer wrote:
>
> Marvin M. Doyley writes:
>
>> Hi there,
>>
>> When I use crossref-add-bibtex-entry it download the BibTeX entry but cannot
>> download the associat
ot;)
(setq bibtex-completion-pdf-symbol "⌘")
(setq bibtex-completion-notes-symbol "✎")
Also enclosed is the backtrace
Thanks for your help in resolving this issue
M
Debugger entered--Lisp error: (wrong-type-argument stringp
("/Users/doyley/Dropbox/Filing_Cabinet/B/ref
nsistently, to
>other formats (HTML or Epub).
This is actually a strong argument. Even though I enjoy writing LaTeX
code, this one is a tough nut to crack with pure LaTeX, where I
achieved the best results with LaTeXML, but it was still lots of work.
May I ask what tooling you use to go from org
Hi Kyle,
You are right. When running emacs without my personal config things work as
described in the manual. I should have verified that first.
My best,
Julian
Kyle Meyer writes:
> Julian M. Burgos writes:
>
>> I have not noticed that org-tree-to-indirect-buffer
>> r
his option is available not only to EXWM users.
Ideally, there should be an option to allow org-tree-to-indirect-buffer to
create more than one indirect buffer if desired.
My best,
Julian
Juan Manuel Macías writes:
> Hi Julian, thanks for your comment.
>
> "Julian M. Burgos"
Hi Juan Manuel,
Thank you, although I tested your functions and compared with the original
org-tree-to-indirect-buffer, the only difference I see is that your function
creates a new exwm workspace. The original function already creates indirect
buffers with their own names (using a slash
Installing bibtex-completion fixed the problem
> On Feb 23, 2021, at 5:53 PM, Kyle Meyer wrote:
>
> Marvin M. Doyley writes:
>
>> Hi there,
>>
>> For some reason org-ref-helm-insert-cite-link is not working anymore
>> for me. When I try to execute i
Thanks Kyle,
I deleted both packages, but the problem still persists.
I am using the latest version of org and help-bibtex-2.0.0 that I just pulled
from Melpa. I also pulled the latest version org-ref
Strange but I will keep digging
Cheers,
M
> On Feb 23, 2021, at 5:53 PM, Kyle Me
this?
Enclosed is the backtrace,
thanks
M
Debugger entered--Lisp error: (error "Command attempted to use minibuffer while
in minib...")
read-from-minibuffer(#("pattern: " 0 9 (face helm-minibuffer-prompt)) nil
(keymap (tab . helm-execute-persistent-action) (normal-state keyma
On 2021-02-15 14:18, Rodrigo Morales wrote:
> 1. Do you use long names?
Usually. Suppose you were doing a bit of genetic programming. You might have a
function that computes the next generation from the current one. You could
write the following snippet that looks suspiciously like pseudocode:
noweb-ref "this is a cool way to do something"
stuff
#+END_SRC
especially as a project grows.
Perhaps we could have a variation on #+NAME that doesn't need to be unique?
Maybe something like #+NOREF, to evoke :noweb-ref? Or #+NONAME?
Sincerely,
Kevin M. Stout
accumulation behavior for duplicate
#+NAME's. It's handy, and users of other literate programming tools will find it
familiar. Also, #+NAME is a nicer per-block syntax than :noweb-ref.
Sincerely,
Kevin M. Stout
leave them
as file-local/buffer-local variables as they are currently. I needed
to read up on how to mark my own variables as "safe" for that purpose,
but I have now found out how to do that.
Thanks for your answer!
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu |For security
ching to that buffer with
`with-current-buffer'.
Now I wonder whether #+BIND is more elegant. But my macro expansion
function modifies a buffer-local variable. Does #+BIND allow for that,
so that the changed value is available in the original org buffer?
-quintus
--
Dipl.-Jur. M. Gülker | https://
ny other link, one example - if it is a PR or a
>>> Github Issue, I'd like it to fetch summary(title) of it and create a
>>> link that looks like this:
>>>
>>> [[https://github.com/user/repo/issues/3899][This issue needs to be fixed
>>> #3899]]
>>
Thanks Bill
> On May 30, 2020, at 11:36 AM, William Denton wrote:
>
> On 30 May 2020, Marvin M. Doyley wrote:
>
>> How do I export the subtree to separate org files, say
>>
>> - Candidate-a.org
>> <https://urldefense.proofpoint.com/v2/u
201 - 300 of 1965 matches
Mail list logo
