d (assuming interest in doing so).
Please let me know!
All the best,
Timothy
(p.s. as mentioned in my first email, I am going to try getting dragged down
this rabbit-hole again till late june)
-latex-regexps, and instead uses it's own hard-coded regexps.
Hopefully it may be possible to tweak this so that once can preview more than
just the defaults hardcoded into org-format-latex.
Warm regards,
Timothy
off for a while now.
I'm also a uni student a few weeks off from exams so I am not able to really
need to resist the urge to jump in and work on implementing these ideas. I
should have significantly more time late june though :)
All the best,
Timothy
-style to easily copy a
link to that position to the clipboard.
From memory modifying this would require overriding a large function, which I
didn't like the look of.
Best wishes,
Timothy
(at this point in time) I am very loosely familiar with the innards
of org (I've just stumbled around loking for specifics with C-h f / C-h v),
so if I look like I'm making any strange/outragous statements, please apply a
substantial pinch of salt :D
Timothy
On May 19 2020, at 3:26 pm, Nicolas
papers signed, it sounds like they may come in handy
:)
Timothy
On May 19 2020, at 3:47 pm, Nicolas Goaziou wrote:
> Hello, Timothy writes: > I love the first-class LaTeX support in Org-mode,
> and discovering that org-edit-special worked inside LaTeX environments was a
> joyous m
ut modifying anything more than org-edit-special and
writing org-edit-latex-fragment ?
Timothy
On May 19 2020, at 5:39 pm, Nicolas Goaziou wrote:
> Timothy writes: > With your comments in mind I started by looking at
> org-edit-special, > and managed to get as far as
> o
Hello All!
I love the first-class LaTeX support in Org-mode, and discovering that
org-edit-special worked inside LaTeX environments was a joyous moment for me.
Shortly after that though, I was disappoint to discover that this didn't work
with inline LaTeX equations \( … \) or LaTeX display
Another email, another request
Hoping that you aren't tired of me yet, I have … (drum-roll) another feature
request!
This time, I'm wanting to be able to use the lovely org latex preview
functionality for more than just the default blocks.
For instance, I'm interested in applying it to mhchem
It's me again!
We're now onto email 2/4. This one is a wish-list of entry points for
customising export functionality (well, styling).
I'm a big fan of trying to make my documents look snazzy with minimal work
(i.e. by cramming all the snazzyness in the back-end), which is why I was
thrilled
Good news! This is the last of my "things I want to contact the mailing list
about" backlog
So, I recently wanted to be able to create a radar chart in org, using #+PLOT
without a 500 character #+PLOT line.
I started with advice-override, but quickly realised it would be better just to
t export backends.
> I don't know HTML enough to help you. You may want to look into headline and
> section filters.
Looks like this can do it for me! I still prefer doing this at-generation, but
I'll take this too.
Seems to be working :)
https://tecosaur.github.io/emacs-config/config.htm
owledge in every output format so as to make sure this
> is consistent everywhere.
I like consistancy, but not enough to sign up for that :P
Timothy.
On May 19 2020, at 9:17 pm, Nicolas Goaziou wrote:
> Timothy writes:
>
> As a side note, I think sending plain text messages, ins
ut modifying anything more than
>> org-edit-special and writing org-edit-latex-fragment ?
> Yes, you (we) can!
Fantastic!
In other news, I have sent off am email to ass...@gnu.org, so hopefully
you'll be able to accept >15 loc patches from me in the (near?) future :)
> Timothy
might be interested in using the org-fragtog MELPA package.
I'm already using it :P
https://tecosaur.github.io/emacs-config/config.html#visuals
> On Tuesday, 19 May 2020 at 15:49, Timothy wrote:
>> #+LATEX_HEADER: \usepackage{mhchem}
>> \ce{CO2} @@latex:\ce{CO2}@@
>
> You prob
that a Gogs issue tracker would prevent anyone from using
the mailing list, but might encourage more people to get involved.
Is there any reason why we can't have both?
Timothy.
On May 19 2020, at 10:58 pm, Bruce D'Arcus wrote:
> Regardless, doing issue tracking, discussion, and patch submiss
Nicolas Goaziou writes:
> I already did, didn't I?
> ...
> That's all for the changes required in `org-edit-special'.
Oh ':) I thought that was just you saying 'it would be something along
the lines of...'
Thanks! I'll let you know when I have something.
> Timothy writes:
&
l' from
>>>> "org.el"
I can't quite see how I would insert this. Since it sounds relatively
simple, if you would be willing to cook up the necessary modification
for me that would be a great help.
On May 19 2020, at 10:09 pm, Nicolas Goaziou wrote:
> Timothy w
If you don't mind me adding 2 more cents :P I don't think that email
should be given up in favour of a web client, or that it isn't better in
many ways.
However, if it were possible to have the best of both worlds, is there a
reason why we'd say no? Just taking a guess here, but I imagine it
> <#part type=“text/x-patch”
> filename=“home/tec.emacs.d/.local/straight/repos/org-mode/0001-Extend-org-edit-special-to-editing-LaTeX-fragments.patch”
> disposition=attachment>
> <#/part>
Well that didn't quite work as intended. Here's a take two.
he read-only
locking working for now :) I think I've got everything else as it should
be, so I should be sending in a patch for feedback shortly :)
Timothy.
ment'
> You also need to add a proper commit message and use `git format-patch',
> and an entry in ORG-NEWS (probably in Miscellaneous part).
I recall being asked to list modified/added functions, what else do I need?
> Bonus points if you can add some tests in
> "testing/lisp/test-org-src.el".
I'll have a look at that, but I'm not quite sure what to do.
> Could you remind me if you signed the FSF papers already?
They're done and dusted :)
Regards,
Timothy.
0001-Extend-org-edit-special-to-editing-LaTeX-fragments.patch
Description: Binary data
ver' references (like cleveref with
> \cref).
>
> As such, I think that the hardcoded \ref should actually be turned into
> a customisable format string, which is what the attached patch does.
--
Timothy
with your patch.
If what I've said above makes sense, I think it would be good to merge .
All the best,
Timothy.
Update: I found the thread, https://orgmode.org/list/87lf90b5ey@gnu.org/
Timothy writes:
> Regarding the Emacs 24.3 requirement, I haven't got the thread on hand
> but IIRC Bastien said that he will bump Org's minimum Emacs to 25 in the
> 9.5 release. As long as I'm not mis-re
is-remembering, the above should be
fine.
--
Timothy
]):
,
| (setq-local jit-lock-defer-time 0.05
| jit-lock-stealth-time 1)
`
This sacrifices immediate font-lock accuracy for responsiveness.
All the best,
*Timothy*
[source]
<https://tecosaur.github.io/emacs-config/config.html#font-display,code--7>
Hi Rémy,
Thanks for bringing this up. This reminds me that we want to get the
French/Japanese translations fleshed out...
All the best,
*Timothy*
Nicolas Goaziou writes:
> Sure, LGTM!
Cool :) Merged.
Now the only other LaTeX PR I may poke you about in the future is the
latexmk one :P
--
Timothy
If anyone else is interested in this, it would be great to get your
thoughts.
I'd also appreciate it if a core maintainer might be able to find the
time to review the patch and let me know if it looks good.
Thanks,
Timothy.
--
> Tom Gillespie writes:
>
>> 1. I think
Hi Sébastien, thanks for your comments.
Sébastien Miquel writes:
> Hi Timothy,
>
> Thanks for your work. I hope this can be merged.
:)
> Here are a few comments.
>
> Doesn't this line in ~org-toggle-inline-results-display~ throw the
> configured delimiters away when cal
two properties should be
> there at all.
It shouldn't be, it should be:
#+begin_example
:body-only t
:html-postamble t
:html-postamble-format ""
#+end_example
Though the last line may need to be
#+begin_example
:html-postamble-format '((en ""))
#+end_example
or similar.
--
Timothy
his, and it should be addressed in
https://code.orgmode.org/bzg/org-mode/commit/7dd667af.
If you could test it and let me know that would be greatly appreciated
:) It seems to work with the manual example for me.
Until I hear otherwise, I'm marking this bug as fixed.
--
Timothy
form as 981f25031.
--
Timothy
Hi Russell,
Have you tried this since
https://code.orgmode.org/bzg/org-mode/commit/ec6d1df9bc8967e1db14bbd3c90828c71a6a8e0e
? Issues like what you mention were exactly the motivation behind your
commit.
--
Timothy
Russell Adams writes:
> I'm enabling paredit globally for all prog-mo
s-mode too.
> Maybe better use something like org-entities?
I'm not sure if that would work, perhaps someone else knows otherwise.
--
Timothy
Thank you for the detailed feedback :)
Ihor Radchenko writes:
> Timothy writes:
>
>>> I do not like abusing prettify-symbols-mode. What if it is not enabled?
If you know of another way of accomplishing text-replacement which
changes back when the cursor enters the region, ple
ult could be a good idea.
> and to the section "Code Evaluation and Security Issues" in the Org manual
> (which does not mention macros).
Looks like this should be updated regardless of the above.
--
Timothy
ch to use oc-csl if citeproc is available, and fall
back gracefully otherwise?
--
Timothy
Hi Léo,
For what it’s worth, I currently make do with:
┌
│ (setq org-highlight-latex-and-related '(native script entities))
│ (add-to-list 'org-src-block-faces '("latex" (:inherit default :extend t)))
└
All the best,
*Timothy*
. merge without FSF
papers) the changes and with a "TINYCHANGE" line at the end of the
commit message --- but I see you've noticed this and have a nicely
formatted commit message, brilliant!
Thanks again, and I hope to see you around,
Timothy.
p.s. For merging hopefully someone like Nicolas
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
I
haven't covered that you'd like to see, along with any other feedback
you may have.
For the next day, you can find the draft at:
https://blog.tecosaur.com/tmio/DRAFT-2021-05-31.html
and then once published it will live at:
https://blog.tecosaur.com/tmio/2021-05-31.html
All the best,
Timothy
e of implementation is
> https://tecosaur.github.io/emacs-config/config.html
>
> Timothy, would you be interested to prepare the patch out of your
> config?
If there's sufficient interest, I'd be happy to cook something up.
I'm not sure it's always desirable though, see:
https://tecosaur.github.
e headings? IIRC it petered out more that
reached a conclusion.
--
Timothy.
Colin Baxter writes:
> It doesn't work for me. I get "No data in plot" in the gnuplot buffer. I
> am probably doing something stupid.
That's odd, it "just works™" for me. Just to check: you are running Org
HEAD?
--
Timothy
rrent-backend' in an export hook.
I see, this sounds like not too much trouble, but I think ideally this
would be OOTB behaviour.
--
Timothy
However, if you do have one and don't want it to be expired, you just
> need to login to the web site every month or so.
You need to log in every month or your account is deleted? If this is
the case, I'm tempted not to bother...
--
Timothy
-latex.el is.
Do share if you have any ideas :)
--
Timothy
want to use to generate 'clever' references (like cleveref with
\cref).
As such, I think that the hardcoded \ref should actually be turned into
a customisable format string, which is what the attached patch does.
--
Timothy
>From db01398de3a29043dbb545ee66006b0b7c0f1368 Mon Sep 17 00:00:00 2
een using this
exact command in my personal config for months now, and it's worked
excellently.
--
Timothy
>From 95806243e40d5f9f19a8db71e2b8b0cd0c5fdb68 Mon Sep 17 00:00:00 2001
From: TEC
Date: Mon, 7 Jun 2021 00:46:09 +0800
Subject: [PATCH] ox-latex: Change default compiler to latexmk
* l
Hi All,
Following on from my comments /ages/ ago, I have done some more work to
improve the HTML export. I intend to push it if I don't hear any
complaints. Please let me know if anything looks dodgy, or if anything
should also be improved with this patch :)
This patch:
- Resolves a W3C warning
this mean that I can't easily have biblatex be used
when exporting to .tex and citeproc used when exporting to HTML?
--
Timothy
is is some profound source of information
return [[i, i^3 - 4*i^2 - 2*i] for i in range(5)]
#+end_src
#+plot: ind:1
#+RESULTS:
| 0 | 1 |
| 1 | -2 |
| 2 | 7 |
| 3 | 8 |
| 4 | 13 |
--
Timothy
Bruce D'Arcus writes:
> Thanks Timothy.
>
> What's your view on modifying current default?
I think latexmk is a pretty reasonable expectation, and your
justification that it's more important seems sound to me.
Using the value seen in my config, I've found that at the least m
Hi Bruce,
In case it's of interest, I've been quite happy with this:
https://tecosaur.github.io/emacs-config/config.html#compiling
Bruce D'Arcus writes:
> While testing org-cite a few weeks ago, I noticed by default bibtex
> won't run with natbib export, or biblatex with biblatex export.
>
>
k you,
> eric
Hope that helps,
Timothy
et a label added with #+name, but I don't know that
there's an easy way to reference it without org-ref. I feel like ideally
this should be something Org provides.
--
Timothy
ure of the feature and perhaps could be shoehorned in
following the merge? I feel like this is one small quite simple case and
most of the thinking required has already been done. I'm not sure
though, I'd go with whatever Nic's thought are on this.
Whichever way this diversion goes, I'm excited to see wip-cite-new merged!
--
Timothy
Matt Price writes:
> Really, I feel like there should be a parade.
There will be one in the next edition of This Month in Org .
--
Timothy
e 1: Some table
│
│ Hey, look at Table 1.
└
I hope this clears up what I was thinking.
All the best,
*Timothy*
name if no :file is set?
I think it would be nice if I could declare a "figures directory"
(default to "/tmp" or "."?) for exactly this.
--
Timothy
d a few default macros.
Unfortunately I have yet to look at the internals of org-lint, so I
can't provide any particular insight, but this does seem like something
which should be supported.
Hopefully someone else will have time to look into this :)
--
Timothy
Hi Eric,
I've not used Org for exporting to BibTeX, so I don't really know what
I'm on about, but is there any particular reason why only some entries
have :url ? Other than that, this seems like a fairly straightforward
patch.
--
Timothy
Eric S Fraga writes:
> I introduced an er
HI Jacopo,
I've just taken a look at your patch and it looks good :) glad to see
you've also followed the commit message format. I hope this gets merged
soon.
--
Timothy
p.s. Just a little note for the future: it's good if you have full
sentences in the description of the changes.
Jacopo De
compilers.
#+end_example
This is rather minor though, I mention this mostly as a note for the
future :)
--
Timothy
Nico Sonack writes:
> Hey there,
>
> I've been using org-mode for quite a while already and am pretty
> happy with it!
>
> Today I noticed a minor oddity, that oc
Marking as closed in favour of 2nd email.
Hi Dave,
Thanks for going to the effort of working out a series of steps to
reproduce the issue, it's most helpful. If you wouldn't mind, do you
think you could try testing the current HEAD/master and seeing if you
still encounter the issue?
--
Timothy
Dave D writes:
> Hi all,
&g
Hi Ihor,
This thread is looking promising! Just wondering if you might have time
to respond to William's latest reply?
--
Timothy
y that can be used
to wrap a section in certain HTML tag(s).
For now though... the best solution would be what Richard suggests.
--
Timothy
Marking as a patch for Woof.
then
start a new thread in a few days).
--
Timothy
William Denton writes:
> On 8 July 2021, Bruce D'Arcus wrote:
>
>> And the implementation challenges raised by John Kitchin and Joost
>> Kremers (namely the candidate list is different) make this better to
>> dea
• a new LaTeX src block syntax highlighting option (this actually isn’t that
much code)
These are all currently maturing in my config, and in particular the “smart
generated export preamble” and new LaTeX syntax highlighting option have been
massaged into a state I’m very happy with over a number of months.
All the best,
*Timothy*
.
--
Timothy
>From 5e6700177f4ef59131c153d985b8eaeb3b303799 Mon Sep 17 00:00:00 2001
From: TEC
Date: Tue, 13 Jul 2021 02:00:38 +0800
Subject: [PATCH] oc-csl: be more caution about the csl etc location
* lisp/oc-csl.el (org-cite-ctl--etc-dir): The previous value of
`org-cite-ctl--etc-
Bastien writes:
> You can consider this an explicit approval :) Even if we do something
> wrong, we can always discuss and revert it.
>
> Thanks!
Pushed :) For future reference, should I be less wary of pushing commits
I'm confident in and haven't had any negative feedback on?
Bastien writes:
> I let Timothy decide.
I consider this patch fit to merge. I'm just under the impression that
this I should only push files I'm listed as a maintainer for without
explicit approval.
--
Timothy
to make the output easier to scan (see https://0x0.st/-mvq.png).
After all this, I just rsync the output directory to my server :)
--
Timothy
Applied in dadbd025f.*
Timothy writes:
> Hi All,
>
> This patch improves the result of running org-plot in the following
> situation
>
> #+plot: ... file:"somefile.png"
>
> [[file:somefile.png]]
>
> Previously, when somefile.png is re-plotted the
"C-c C-c" executed
>org-plot/gnuplot when on such a #+PLOT line.
>
> 2. why does point move to the next line when I do execute the command?
>This is somewhat annoying when playing around with the settings. It
>would be nice to have point remain where it is.
&g
Thank you for bringing this up, and bisecting the error. Interesting
that this hasn't been noticed/reported till now.
>From a quick test myself, this appears reproducible, though I have no
idea what's going on (yet). Please let me know if you find anything.
--
Timothy
ian martins wri
)
((or `timestamp (and `planning (guard (org-at-timestamp-p 'lax
(org-timestamp-change 0 'day))
((and `nil (guard (org-at-heading-p)))
--
2.31.1
Eric S Fraga writes:
> On Monday, 26 Apr 2021 at 16:24, Timothy wrote:
>> A while ago Eric raised two nice suggestions. (2) has just b
ing (guard (org-at-timestamp-p 'lax
(org-timestamp-change 0 'day))
((and `nil (guard (org-at-heading-p)))
--
2.31.1
Sorry for the noise,
Timothy
Timothy writes:
> Since you don't seem to have pushed yet, here's an updated patch that
> takes into account Nicolas' comments.
... and that patch didn't take into account the need to escape "+" in
the regex.
Take 3.
>From 4e5fcb4726711ff356656cb6fccf6e341656443d Mon Sep 17
> with set output and directory paths set with set loadpath and set
> fontpath.
Wouldn't this be sufficient?
--
Timothy
Bruce D'Arcus writes:
> Hmm .. org doesn't have an inline quote, I guess?
I don't think so, unless @@quote:@@ is recognised.
--
Timothy
you can do things (backticks and
spaces for code), and I'd think supporting a set like: Gruber's
original, commonmark, and GFM would make sense.
Alternatively, we can leave that to other backends like ox-gfm.
Basically: markdown is a mess and I'm not sure what would be a good
course of action.
--
Timothy
Bastien writes:
> I suggest having a new https://orgmode.org/manuals.html page
> Timothy, WDYT?
I've seen a few manual-related requests like this but held off from
doing anything from a concern about clutter. Now that you mention it, I
think a dedicated page would make a lot of sense
ch so far
back. If it was a standalone thing, I could see it, but as it's
vendored with Emacs I'm not sure why we don't just do stable Emacs - 1
(i.e. 26.3 ATM).
--
Timothy
Now that Eric and I have both tested this, and Nicolas' comments have
been taken into account, it would be great if a core maintainer could
consider applying this patch :)
--
Timothy
p.s. I'm specifically making a new reply to the version of the patch
that should be looked at, in the hope
"こんにちは.example" is converted to
> "xn--28j2a3ar1p.example".
>
> Punycode is available in Emacs through libidn (2)
Thanks! I'm now making use of it as of
https://github.com/tecosaur/emacs-config/commit/1ccbadd
--
Timothy
quick-fix, but I find it odd
that this is a issue, and am yet to be able to reproduce this myself.
Is anybody else willing to try this and weigh in?
--
Timothy
p.s. Good luck with the presentation!
hecked the docs for `org-table-recalculate' and based on manually
calling it compared the behaviour to C-u C-c C-c on a table and noticed
no difference, but I'm not familiar with the intended functionality so
an example from Eric (or someone else) of what should happen would be
very helpful.
--
Timothy
te proposal for this.
Will do once I've thought a bit about what would be a good
interface/implementation for this.
> Once all issues listed here are handles, please close the call for
> help with "X-Woof-Help: close" as a header.
Will do
Thanks for reminding me about this,
Timothy.
Bastien writes:
> Applied in master as commit b90b850ae.
>
> Can you add a etc/ORG-NEWS entry for this?
Great! News entry added.
--
Timothy
short term.
I'm not quite sure what you mean by a hybrid system, but I think
generating informative references based on header content is a nice
improvement that also make links much more stable.
Forgive me if this is an overly simplistic quicktake.
--
Timothy.
t if you want to take
> a peek, here is a coupon code for you to get it for free (the coupon is
> valid for a week)!
>
> https://leanpub.com/hacking-your-way-emacs/c/f23s5unGtLf0
>
> Best,
Interesting. I wanted to take a peek but I can't see how to view it for
free ... I may be blind though.
--
Timothy
Hi pillule, should we consider this patch cancelled?
pillule writes:
> You are right I clearly missed org-src-ask-before-returning-to-edit-buffer
> Don't know how . . .
>
> Sorry for the noise.
ts"
Thanks for the patch :)
Timothy
ed blocks (e.g. src and example blocks) it appends
",{block}--{n}", for example: "some-header-string,code--1".
I consider this to be quite a nice improvement.
--
Timothy
pointed out some concerns I have about the robustness of this system
> already.
If there are any other concerns than what I've covered above, I'm afraid
they have slipped past me.
--
Timothy
1 - 100 of 640 matches
Mail list logo
