Hello,
Timothy writes:
> 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 \ce{ … }
> fragments, as well as siunitx \SI{ … }{ … }.
I think you can preview
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 moment for me.
> Shortly after that though, I was disappoint to discover that this
> didn't work with inline LaTeX equations \( … \)
Hello,
Kyle Meyer writes:
> It bisects to b4e91b7e9 (New function: org-collect-keywords,
> 2020-04-26). I haven't done much digging, but I was able to restore the
> behavior with the change below, which may be a bad idea for other
> reasons.
>
> diff --git a/lisp/org.el b/lisp/org.el
> index
Hello,
Timothy writes:
> We're now onto email 2/4. This one is a wish-list of entry points for
> customising export functionality (well, styling).
Export framework has *many* entry points already.
See (info "(org)Advanced Export Configuration")
> I'm a big fan of trying to make my documents
On Mon, May 18, 2020 at 06:13:38PM -0500, James R Miller wrote:
> Doesn’t Gogs have a nice issue tracker functionality?
I looked up Gogs. Needs javascript *and* cookies. Wake me up when
there's a plain, straight service which works without any of them.
Cheers
-- t
signature.asc
Description:
> It would need proof reading, and comparing with "org-element.el", the
> actual implementation of the syntax. Formalization may be better better,
> too.
I didn't know that there was a single point of entry to parse elements. I think
my first step will be to try to write spec tests in elisp
Hi Nicolas,
Thanks for getting back to me on this. With regard to
> I think you can preview \ce{...} just fine, with appropriate LaTeX headers.
I'm entirely likely to be missing something, however from a minimal test in a
document I'm unable to get org-latex-preview to do anything with the
Timothy writes:
> Once again, thanks for taking the time to respond. I can assure you
> that it's much appreciated :)
You're welcome.
> By item filter, I assume you are referring to
> org-export-filter-item-functions. That looks quite promising. I just tried a
> minimal function to testit
>
Hi Nicolas,
Thanks for the pointers. Taking your hint :P I took a look to see what I might
be in for.
With your comments in mind I started by looking at org-edit-special, and
managed to get as far as org-element--current-element: but at this point I'm
stumped.
I'll look into getting FSF
Timothy writes:
> With your comments in mind I started by looking at org-edit-special,
> and managed to get as far as org-element--current-element: but at this
> point I'm stumped.
It sounds like you took the opposite route. I suggested to first write
a function, `org-edit-latex-fragment'.
Yes, the behavior changed. Now the author macro expands to blank despite
the variable user-full-name is set.
Note I use #OPTIONS: author:nil, which is necessary to prevent that the export
is concluded by an author line.
The expected behavior is to expand to the value of user-full-name.
Am Mo.,
Nicolas,
> It sounds like you took the opposite route. I suggested to first write a
> function, `org-edit-latex-fragment'.
I wanted to see how it would fit in first ¯\_(ツ)_/¯
> Once done, you can insert it in `org-edit-special', but it boils down to
> adding a line there, right below
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm write an extension to beautify org link with colors and unicode icons for
better intuitive looks. But I don't know how to write those functions.
I checked out this info page ([[info:org#Adding Hyperlink
Types][info:org#Adding Hyperlink
My go to reference is
https://kitchingroup.cheme.cmu.edu/blog/2016/11/04/New-link-features-in-org-9/
J
On Tue, May 19, 2020 at 6:56 AM stardiviner wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> I'm write an extension to beautify org link with colors and unicode icons
> for
>
On Tuesday, 19 May 2020 at 10:02, Timothy wrote:
> As this currently stands, with the below table and plot line I can
> produce this plot https://media.githubusercontent.com/media/tecosaur/
> emacs-config/master/misc/document-format-comparison.png.
This looks very nice and I would use it if it
I don't have any specific comments, but it looks great in general, and
I'd use it!
On Tuesday, 19 May 2020 at 15:49, Timothy wrote:
> #+LATEX_HEADER: \usepackage{mhchem}
> \ce{CO2} @@latex:\ce{CO2}@@
You probably need to add this to =org-latex-packages-alist= in your
emacs configuration:
(add-to-list 'org-latex-packages-alist '("version=3" "mhchem"))
Also, you might be
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
Nicolas,
> You asked for it, though, using `pp'.
I guess I did, didn't I
> is just a string, with properties attached. If you simply return `text', you
> will only see "string"
Good to know, thanks :)
>> I still feel that it would be nicer to have the body of this cl-case (from
>>
Hello,
Ihor Radchenko writes:
>> As you noticed, using Org Element is a no-go, unfortunately. Parsing an
>> element is a O(N) operation by the number of elements before it in
>> a section. In particular, it is not bounded, and not mitigated by
>> a cache. For large documents, it is going to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bellowing is my source code, it does not work. I'm wondering why?
#+begin_src emacs-lisp
(defun org-link-beautify-face (link)
"Set link face colors."
(let ((raw-link (org-element-property :raw-link link))
(type (org-element-property
Timothy writes:
As a side note, I think sending plain text messages, instead of HTML, is
better, at least on a (this?) mailing list.
> Indeed. Though my 2c on this sort of thing that the most important
> factor is consistency. IMO if org-html-checkbox-types exists, then an
> equivalent should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John Kitchin writes:
> My go to reference is
> https://kitchingroup.cheme.cmu.edu/blog/2016/11/04/New-link-features-in-org-9/
Really thanks, John. I have read your blog article. Found most of link
parameters examples. But still confused me, I'm
Nicolas Goaziou writes:
> As a side note, I think sending plain text messages, instead of HTML,
> is better, at least on a (this?) mailing list.
Good news on that front --- I didn't think my mail client did that, turns
out that it does :)
> This argument doesn't scale. There's no guarantee an
I don't know if :display is for that, I think it is mostly related to
should a link with description only show the description, or should it be
full and show link and description.
You probably want the :activate option, where you could use something like
an overlay on the link. I don't have time
Nicolas Goaziou writes:
> LaTeX fragments are at a lower level than plain "elements", so
> `org-element-at-point' does not see them.
I see. Might you be willing to do & show me the modifications needed to
use the `latex-fragment case?
>> Can I really get away without modifying anything more
(I also don’t understand the knee jerk response away from cookies /
JavaScript). Those are just parts of the modern web... Cookies for state and
persistent login and JavaScript for making the web page interactive.
Are you saying you’d want some sort of REST api instead and the website would
Timothy writes:
> I see. Might you be willing to do & show me the modifications needed to
> use the `latex-fragment case?
I don't understand your question.
On May 19 2020, at 7:45 pm, Eric S Fraga wrote:
> You probably need to add this to =org-latex-packages-alist= in your
emacs configuration:
> (add-to-list 'org-latex-packages-alist '("version=3" "mhchem"))
I tried adding that. Didn't change anything.
> Also, you might be interested in using the
Thanks Eric,
I will give it a try
Cheers,
M
> On May 19, 2020, at 10:14 AM, Eric S Fraga wrote:
>
> On Tuesday, 19 May 2020 at 09:19, Marvin M. Doyley wrote:
>> I have decided to take the plunge and switch to mu4e. I have also
>> installed the org-mu4e package. Most stuff works pretty well,
Hello,
"James R Miller" writes:
> This just might be the functionality that makes me learn elisp. :)
See. You'll soon thank me for removing the feature you liked ;)
Regards,
--
Nicolas Goaziou
Timothy writes:
> In your original email you wrote
> The new function can then be installed in `org-edit-special' 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
Regardless, doing issue tracking, discussion, and patch submission on a ML
in 2020 is pretty odd and inefficient.
I would have submitted feedback here 6-12 months earlier than I did if org
had a proper issue tracker.
On Tue, May 19, 2020, 3:35 AM wrote:
> On Mon, May 18, 2020 at 06:13:38PM
I can't help but chime in here. Using email for project management, patches,
testing, etc is not difficult or unusual.
In fact, the Linux kernel uses email for this purpose. They have a variety of
reasons which were recently covered in some articles. Clearly their code base
and number of
My apologies. I thought Gogs was the repository for org as I that is what is
linked from the homepage.
--
James Miller
james.ryland.mil...@gmail.com
Hello,
"Dauer, Michael" writes:
> Yes, the behavior changed. Now the author macro expands to blank despite
> the variable user-full-name is set.
> Note I use #OPTIONS: author:nil, which is necessary to prevent that the export
> is concluded by an author line.
>
> The expected behavior is to
On Tue, May 19, 2020 at 09:05:33AM -0500, James R Miller wrote:
> (I also don’t understand the knee jerk response away from
> cookies / JavaScript).
Mine isn't a knee-jerk reaction. It's worse: it's well thought-out.
Discussing that in detail would be far off-topic for this list,
though.
> Those
Hi Eric,
This works like a charm.
Thanks,
M
> On May 19, 2020, at 10:14 AM, Eric S Fraga wrote:
>
> On Tuesday, 19 May 2020 at 09:19, Marvin M. Doyley wrote:
>> I have decided to take the plunge and switch to mu4e. I have also
>> installed the org-mu4e package. Most stuff works pretty well,
My 2c: Having a github-esque pubic issue tracker is good for accessibility — in
the sense of ease of access to new-comers.
Personally, this is the first time I've engaged in technical discussions on a
mailing list, and needing to use a ML did feel like an extra hurdle.
I wouldn't imagine that a
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:
>
>> In your
On Mon, May 18, 2020 at 7:30 PM Kyle Meyer wrote:
>
> It bisects to b4e91b7e9 (New function: org-collect-keywords,
> 2020-04-26). I haven't done much digging, but I was able to restore the
> behavior with the change below, which may be a bad idea for other
> reasons.
>
Thanks for that bisect!
Hi there,
I have decided to take the plunge and switch to mu4e. I have also installed the
org-mu4e package. Most stuff works pretty well, except latex equations are not
rendered when I send them.
Does anybody know how to solve this problem?
Thanks,
M
Timothy writes:
>> It sounds like you took the opposite route. I suggested to first write a
>> function, `org-edit-latex-fragment'.
> I wanted to see how it would fit in first ¯\_(ツ)_/¯
Sure. That's a good way to learn stuff. In this case, it's not the
easiest one, though.
>> Once done, you
On Tuesday, 19 May 2020 at 09:19, Marvin M. Doyley wrote:
> I have decided to take the plunge and switch to mu4e. I have also
> installed the org-mu4e package. Most stuff works pretty well, except
> latex equations are not rendered when I send them.
>
> Does anybody know how to solve this problem?
mist.org>>>
* test
foo {{{author}}} bar {{{keyword(AUTHOR)}}}
{{{title}}}
{{{date}}}
{{{time}}}
{{{input-file}}}
{{{n}}}
<<<
ascii output buffer>>>
Michael Dauer
Table of Contents
_
1. test
1 test
==
foo bar
mist.org
1
<<<
Am Di., 19. Mai 2020 um 16:11 Uhr
The face function only takes the link path, which is a string. you cannot
use org-element-property on it.
Maybe you want something like this:
#+begin_src emacs-lisp
(defun org-link-beautify-face (path)
"Set link face colors."
(message "beautifying")
(if (and (not (file-remote-p path))
Nicolas Goaziou writes:
>> I see. Might you be willing to do & show me the modifications needed to
>> use the `latex-fragment case?
> I don't understand your question.
In your original email you wrote
The new function can then be installed in `org-edit-special' from
"org.el"
I can't
"James R Miller" writes:
> So, I definitely agree that using Github / Gitlab does expose you to
> tracking messes and that is something to shun. I figured a self-hosted
> Gogs instance (which is already being hosted at
> https://code.orgmode.org/bzg/org-mode) would fix the "tracking" issue.
>
>
On Wed, May 20, 2020 at 01:03:50AM +0800, Timothy wrote:
> 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
>
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
So, I definitely agree that using Github / Gitlab does expose you to tracking
messes and that is something to shun. I figured a self-hosted Gogs instance
(which is already being hosted at https://code.orgmode.org/bzg/org-mode) would
fix the "tracking" issue.
I think an actual issue tracker has
+1
Le 18/05/2020 à 09:23, Timothy a
écrit :
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
On Tue, May 19, 2020 at 15:49 Russell Adams
wrote:
> Is there a problem with submitting issues via the mailing list? Has
> something
> gone unaddressed? Do you have any statistics to show that there is
> decreased
> participation because you have to use email? Is something really
> inefficient
Sourcehut seams interesting. Did you know if importing github/gitlab
projects, with issues and merge requests (opened and closed) is supported
at the moment?
I noticed it is in alpha, so I don't expect to see all the features of any
of those forges yet.
Before I forget, Does magit+forge works
On Tue, May 19, 2020 at 01:50:26PM -0500, James R Miller wrote:
> I think an actual issue tracker has merit to large projects.
>
> And I don't think simply saying "we've always done it through a ML" or "$FOO
> project is bigger than us and uses a ML" is good enough. $FOO project may very
> well
Roland Everaert writes:
> Sourcehut seams interesting. Did you know if importing github/gitlab
> projects, with issues and merge requests (opened and closed) is supported
> at the moment?
I did a bit of googling, and couldn't find anything, no. The developer
is very responsive, though, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John Kitchin writes:
> The face function only takes the link path, which is a string. you cannot
> use org-element-property on it.
>
> Maybe you want something like this:
>
> #+begin_src emacs-lisp
> (defun org-link-beautify-face (path)
> "Set
Hi all,
Interesting discussion. I have also wondered about this - I have not
yet contributed to the Org codebase, but I have wondered if patches
and bug fixes can sometimes get lost among other discussions.
However, ultimately the best tracking system is the one that works for
the developers and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John Kitchin writes:
> I don't know if :display is for that, I think it is mostly related to
> should a link with description only show the description, or should it be
> full and show link and description.
>
> You probably want the :activate
Hello,
"Dauer, Michael" writes:
> mist.org>>>
>
> * test
> foo {{{author}}} bar {{{keyword(AUTHOR)}}}
> {{{title}}}
> {{{date}}}
> {{{time}}}
> {{{input-file}}}
> {{{n}}}
> <<<
>
> ascii output buffer>>>
> Michael Dauer
>
>
> Table of Contents
> _
>
> 1. test
>
>
> 1 test
>
On 5/19/2020 1:48 PM, Russell Adams wrote:
> On Tue, May 19, 2020 at 01:50:26PM -0500, James R Miller wrote:
>> I think an actual issue tracker has merit to large projects.
>>
>> And I don't think simply saying "we've always done it through a ML" or "$FOO
>> project is bigger than us and uses a
Nils Schween writes:
> ("d" "Diary entry" entry (file+datetree+prompt
> "~/MPIK-Nextcloud/emacs/.org/kalender.org")
> "* %i%?\n %T")
>
> And it works as expected: When calling the capture template, I am prompted
> for a
> date and I can also type a time, and on saving
> This idea that the tools used by a potential contributor are inadequate
> misses the point. If the intention is to keep a project going, or better
> yet increase the number of contributors, tools have to be used that will
> be convenient and familiar to those thinking about contributing.
>
>
Nicolas Goaziou writes:
> At first glance, it looks harmless. If the test suite passes, we can
> apply it.
The test suite does pass with the change. Pushed, along with a
regression test (962b8e765).
Thanks.
Nick Daly writes:
> Attached is an updated patch that makes output trimming work with
> blocks that do and don't produce results. The old patch creates a
> =let: Wrong type argument: arrayp, nil= error when evaluating blocks
> that don't produce output. This necessarily incorporates yesterday's
68 matches
Mail list logo
