Hi All,
Short version
t...@tecosaur.com ⟶ g...@tecosaur.net (in commits) *
tecos...@gmail.com ⟶ orgm...@tec.tecosaur.net (in communications here)
* I've sent this email from the (old) commit address to leave a paper
trail so
it's (hopefully) clear to anybody who searches for the
Tim Cross writes:
> I also had to install textlive, plantuml, graphviz, taskjuggler,
> ledger, sqlite and many other things.
Perhaps it would be good to make a table of
| software | needed for | package name | download page |
and/or prompt users when an action requiring another executable
All good points, but I'll just quickly respond to this:
Daniele Nicolodi writes:
> Please understand that the GSoC is not a way to get labor for the
> project sponsored by Google: it is very likely that the time investment
> required to the mentors would be more than enough to implement what
Jose E. Marchesi writes:
>> Google's SoC organisation applications are currently open, and close on
>> <2020-02-20>. I know that Org participated once, in 2012.
>>
>> Would it be a good idea to submit an application to do so again?
>> With the rise in interest in computational notebooks,
Hello All,
Google's SoC organisation applications are currently open, and close on
<2020-02-20>. I know that Org participated once, in 2012.
Would it be a good idea to submit an application to do so again?
With the rise in interest in computational notebooks, blogging tools,
and other features
Uwe Brauer writes:
> Aha, thanks, it works, sometimes:
>
> The first two work, the last two not. Not sure what to think about it
Mmm, you need to have #+attr_html immediately followed by the link on
the next line.
It would be nice if there was a way to set these attributes inline with
the
Luca Ferrari writes:
> Hi all,
> I'm using org to produce beamer presentations, and I've a lot of src blocks.
> Is there any way to emphasize words or lines within such blocks? For
> example to place the command arguments in bold face?
>
> Thanks,
> Luca
I'd have to look at the manual for
Uwe Brauer writes:
> I need to produce a html file, with links opening new tabs (pages) as in
>
> https://apps.apple.com/es/app/radar-covid/id1520443509;
> target="_blank">Descarga Directa
>
> However
>
> [[https://www.mpic.de/4747361/risk-calculator target="_blank"][Simulador de
> riesgo
Hi Kyle, All,
As requested, here's a small documentation entry for the new setting :)
>From 636330422eef59f448a60b933be9a5581af9 Mon Sep 17 00:00:00 2001
From: TEC
Date: Mon, 1 Feb 2021 03:01:12 +0800
Subject: [PATCH] manual, news: Document org-html-meta-tags
* docs/org-manual.org, etc/
Eric S Fraga writes:
> I actually tell (warn?) my students that spreadsheets are an example of
> a "write-only programming language", the other being APL (for those with
> long memories).
I may not be of the right generation to remember APL, but I used to love
spreadsheets ... until I had to
Kyle Meyer writes:
> I've applied this (a8df7670c) with two minor changes (shown in the diff
> at end): s/with with/with/ in a docstring and move an element to its own
> line to avoid the warning from lisp-mode's lisp--match-hidden-arg.
Thanks :)
> This thread has gone on long enough that
Gah! I left the subject as a placeholder [shame emoji].
Apologies for that.
Why do I always seem to notice these things as the Email is sending...
--
Timothy
TEC writes:
> Hi All,
>
> This is just some tweaks to the styling in ox-html that I think may
> appeal (and prevent ridic
the best,
Timothy.
>From 635bd77cd7a2dc55cc0705c5bbf2e11091bfbaf3 Mon Sep 17 00:00:00 2001
From: TEC
Date: Wed, 20 Jan 2021 16:37:29 +0800
Subject: [PATCH 1/5] ox-html.el: remove CDATA strings
* lisp/ox-html.el (org-html-scripts, org-html-style-default,
org-html-infojs-template): remove CD
This thread has dragged on ages, and if no-one else is following this
chain I wouldn't blame them in the slightest.
To help indicate that this is actually ready (at last) now, I'm just
going to add that info the the subject line in the hope it helps Bastien
or any others notice that this is
TEC writes:
>> Sorry, I still see the flycheck warning and "amp;" for "&".
> Maybe I accidently sent you the old patches? I'll check tomorrow.
Hah, I check and guess what I see? The changes were unstaged .
Sorry about that, here's an ac
Jens Lechtenboerger writes:
> Sorry, I still see the flycheck warning and "amp;" for "&".
Maybe I accidently sent you the old patches? I'll check tomorrow.
--
Timothy.
08c8cfa4b0bf11842907c31846832f1a Mon Sep 17 00:00:00 2001
From: TEC
Date: Mon, 14 Dec 2020 17:41:33 +0800
Subject: [PATCH 1/2] lisp/ox-html.el: make html meta tag builder nicer
* lisp/ox-html.el (org-html--build-meta-info): Multi-line repeated
structure extracted to new function `org-html--build-
r the doc
> string (typos, active voice):
> Use document's plist INFO to derive relevant information for the tags.
Sounds good. Done.
--
Timothy
>From f3f7325ea77cc443387e69f65e899a9537606d80 Mon Sep 17 00:00:00 2001
From: TEC
Date: Mon, 14 Dec 2020 17:41:33 +0800
Subject: [PATCH 1/2] lis
attached :)
--
Timothy.
>From de74dcbd51703439faafe96cbc1c60965f064eaa Mon Sep 17 00:00:00 2001
From: TEC
Date: Mon, 14 Dec 2020 17:41:33 +0800
Subject: [PATCH 1/2] lisp/ox-html.el: make html meta tag builder nicer
* lisp/ox-html.el (org-html--build-meta-info): Multi-line repeated
structure extr
Juan Manuel Macías writes:
> Thank you very much for your response and your comments.
Seriously, thanks for the patch. I think the ML is usually a bit more
responsive, but it seems to be a bit quiet at the moment.
> I agree to name "Insert, include, etc." the attribute to include
> arbitrary
Hi Juan,
Thanks for your patch.
This looks like a fairly sensible addition. Two comments from me:
1. I'm not sure that "options" is a good name for arbitrary LaTeX which
is included inside the verse block. Perhaps something like "insert"
or "include", etc. may be a better fit.
2. It's
Hi Juan,
Since you've resent this in a second email, let's discuss this patch
there.
As such, I'm marking this patch as closed.
--
Timothy.
Hi turbo.
As this appears to be an exact duplicate of your other email, I'm going
to mark this as closed and hope that any/all conversation on your patch
happens there.
--
Timothy
Thanks for the patch turbo.
I was able to test this with a simple Org file, and both observed the
issue with radio targets in generated markdown files, and observed the
patch fixing it, as intended.
--
Timothy
turbo.c...@clovermail.net writes:
> exporting to markdown loses radio target
Hi Jack,
I love the look of this! Thanks for submitting a patch.
Sorry it's taken so long for someone to take a look at it, I think a lot
of the 'main' Org people have been pretty busy over the last few months.
I just tried to give this a shot.
First up, I had to remove the ORG-NEWS part of
Sep 17 00:00:00 2001
From: TEC
Date: Mon, 14 Dec 2020 17:41:33 +0800
Subject: [PATCH 1/2] lisp/ox-html.el: make html meta tag builder nicer
* lisp/ox-html.el (org-html--build-meta-info): Multi-line repeated
structure extracted to new function `org-html--build-meta-entry'.
The keyword value formatt
Gustav Wikström writes:
> It is my believe that Org would benefit from a counter that would "tic
> up" even if no one collects the money. Like it or not, money has an
> effect. Better to allocate it to open source work than anything else! Or?
I've never used it, but could something like
t job. thank you.
>>
>>
>> On 12/27/20, Samuel Wales wrote:
>>> i like the black bg, the no issues with paragraph width.
>>>
>>>
>>> On 12/22/20, TEC wrote:
>>>> Hi all,
>>>>
>>>> This is a quick patch to us
H] org-plot.el: fix compiler warnings
>>
>> * (org--plot/values-stats): Replace `log10' with `log'.
>
> Please add a file name ("lisp/org-plot.el") to the start of the
> changelog entry.
Ah, forgot I needed that. Sorted :)
(final?) patch revision attached.
--
Timothy
>Fro
indentation of the arguments is thus also changed.
> The mapcar is unnecessary; you can reposition (lambda ...) as
> mapconcat's FUNCTION argument.
Thanks for spotting that. Resolved.
Updated patch attached. Let me know how it looks to you :)
--
Timothy
>From 22717d0750e2c001003b45f1d48
TEC writes:
> Kyle Meyer writes:
>
>> This series introduced some compiler warnings.
>>
>> Timothy, could you please submit a follow-up patch to address these?
>
> Absolutely. Thanks for raising this, I'll take a look shortly.
Here we go :)
>From 309907af5e7
Kyle Meyer writes:
> This series introduced some compiler warnings.
>
> Timothy, could you please submit a follow-up patch to address these?
Absolutely. Thanks for raising this, I'll take a look shortly.
--
Timothy
be an easy upgrade to our online documentation :)
--
Timothy
>From fc57ea88432ea119d063906cc29cc51ee591031d Mon Sep 17 00:00:00 2001
From: TEC
Date: Wed, 23 Dec 2020 10:30:09 +0800
Subject: [PATCH] mk/default.mk: use same html doc style as emacs
* mk/default.mk: Add CSS stylesheet ref to H
I've been following this conversation, and I'm glad to see it happening.
However, we've really stayed quite far from the subject of our emails :P
I think this conversation deserves it's own thread, perhaps something
like "Org's development forge".
--
Timothy
Lennart C. Karssen writes:
>
Jens Lechtenboerger writes:
>> For people who want to customise this to add metadata, the page title is
>> something they're probably interested in.
>
> What metadata would you derive from the title?
In my earlier example, I use the "og:title" property.
>> If so, I think it's work giving the
Jens Lechtenboerger writes:
>> For people who want to customise this to add metadata, the page title is
>> something they're probably interested in.
>
> What metadata would you derive from the title?
In my earlier example, I use the "og:title" property.
>> If so, I think it's work giving the
I don't think this should be forgotten about, so I'm adding it to
https://updates.orgmode.org/#help for now.
Jens Lechtenboerger writes:
> I like this!
:)
>> Maybe it should be applied to the rest (in ~org-html--build-meta-info~)?
>> I'm not sure.
>
> I’m not sure either. Maybe people expect their typed characters,
> maybe not. This might call for a new variable.
I'm tempted to leave the current
Hello. I just have a few cents I'd like to add.
Bastien writes:
> Thanks a lot for the kind words, appreciated.
You deserve them! :)
> ... but I'm very receptive to the real questions: how can we expose
> the latest Org to more testers? how can we recruit more contributors?
I actually have
rates such a list. No more mixing of the two.
How does this look?
Timothy.
>From 9848af808752bc03404befaab7ab5ebb902aa1d0 Mon Sep 17 00:00:00 2001
From: TEC
Date: Mon, 14 Dec 2020 17:41:33 +0800
Subject: [PATCH 1/2] lisp/ox-html.el: make html meta tag builder nicer
* lisp/ox-html.el (org-html--
Hi Jean,
Please read my previous emails before re-iterating the same points.
LSP is not patented, it's just referenced in a patent about MS's fancy
remote development extension.
Jean Louis writes:
> Enrich it with unencumbered patent-free solutions.
That's what I'm doing :)
--
Timothy.
Jean Louis writes:
> Microsoft have filed patent for LSP languag server protocol:
> https://uspto.report/patent/app/20190149346
This isn't a patent for LSP (it's an open standard), this is a patent
for their Remote Development package:
Russell Adams writes:
>> I do see your point. I think in order to warrant being presented as a
>> one-step-from-the-homepage target it would be good to tidy up the Worg
>> homepage.
>
> That's a valid criticism. Worg's main page could use an update to look
> more like the main site.
>
> Does
Russell Adams writes:
> REST API calls to a remote server as a core part of editing text in
> your editor isn't concerning? How remote? How would you know? If they
> use HTTPS could you even see what is sent?
I'm not concerned about REST API calls to a remote server, because:
1. There are no
Hi Neil,
Nope! That’s the nice thing, those are all currently features of the LSP
protocol .
All the best,Timothy
From: ">Neil Jerram
Subject: Re: Emacs as an Org LSP server
To: ">TEC
Cc: "org-mode-email"
Date: Tue, 15 Dec 2020 01:57:27 +0800
Yes, thanks,
Russell Adams writes:
> LSP is also REST based, so your editor how has to talk to a web
> *server* over a network. This could be central, and not just on your
> machine. How would you know in an update that didn't happen?
This just ... isn't right.
It's not even REST based, it's using
stuff like table alignment, checkbox state propagation…
Does that help?
All the best,Timothy
From: ">Neil Jerram
Subject: Re: Emacs as an Org LSP server
To: ">TEC
Cc: "org-mode-email"
Date: Tue, 15 Dec 2020 01:22:55 +0800
I'm afraid things still aren't clear for m
Jean Louis writes:
> [LSP is a evil plot from microsoft]
Hi Jean,
I can see that you're overly concerned about Microsoft being able to
somehow exert control over this. It may assuage your concerns to see an
example "technology stack" that Org-LSP could fit into.
1. Org / Emacs, all GPL-3
2.
Russell Adams writes:
> One could argue that "Releases", "Updates", and "Install" should be
> merged into a common download link. They all are the same thing. ;]
Hmmm. "Updates" seems like a bit of a special thing, but perhaps some
merging could happen sensibly. If that could be worked out,
Eric S Fraga writes:
> Conclusion is that there is no conclusion.
Sounds about right .
Thanks for the link Eric.
--
Timothy
that clear things up for you? You can also see https://langserver.org/.
All the best,Timothy
From: ">Neil Jerram
Subject: Re: Emacs as an Org LSP server
To: ">TEC
Cc: "org-mode-email"
Date: Mon, 14 Dec 2020 23:46:12 +0800
Thanks Timothy. I did read the README, bu
Bastien writes:
> FWIW, I just slightly updated this page with this paragraph:
>
> If you are not a subscriber to the list, you can still send an email
> to emacs-orgmode@gnu.org, we will add you to the whitelist of people
> who can reach the list.
>> As a second request, can we get a link
e: Emacs as an Org LSP server
To: ">TEC
Cc: "org-mode-email"
Date: Mon, 14 Dec 2020 19:41:05 +0800
Could you describe a use case? Apologies if I missed this in earlier threads.On Sun, 13 Dec 2020 at 10:44, TEC <tecos...@gmail.com> wrote:
A little progress update.https://github.co
Bastien writes:
> Can we approach this with two patches, one with the refactoring and
> one with the added functionality?
Sure :) I'll take care of this when I get home in a few hours.
> This sounds useful.
Glad to hear!
> I think "Org Export" as the default is counter-intuitive, let's
Bastien writes:
> Let's wait for Jens feedback on this patch, since he took care of
> testing it so far.
Assuming Jens responds as he usually has (relatively promptly), this
sounds good to me :)
> In a nutshell, can you restate what problem is this patch fixing?
There are two things I
Bastien writes:
> Applied, with minor modifications of the changelog entries:
>
> - You need to add an entry when creating a new custom variable.
>
> - I suggest saying "option" instead of "custom variable".
>
> - Sentences should be separated by two spaces and start with an
> uppercase
Hi Jean, a few thoughts.
Jean Louis writes:
> In other words program like Org capture is not meant for people having
> too many templates and that shall be explained right away both in
> function definitions and in the manual. Important people lose their
> time and effort in customizing org
Jean Louis writes:
> * TEC [2020-12-13 13:44]:
>>
>> A little progress update.
>>
>> https://github.com/tecosaur/org-lsp now exists.
>
> As Org-mode does not have collaboration neither was initially designed
> for other editor, such idea is welcome.
>
381aff7562df96945aa58838ad966aa9211 Mon Sep 17 00:00:00 2001
From: TEC
Date: Thu, 17 Sep 2020 21:27:18 +0800
Subject: [PATCH] lisp/ox-html.el: make html meta func nicer
* lisp/ox-html.el (org-html--build-meta-info): Multi-line repeated
structure extracted to new function `org-html--build-meta-entry'
Hi Ian,
Sorry for the slow response, I'm marked your email though, so I'm now
getting back to you :)
ian martins writes:
> I wanted to change line colors but didn't find a way. Is there a way?
Indeed! Though I do it with lisp, and using my patches.
I think I saw a patch about multiline
Just a quick note on the values proposed.
All of the Alt Ns have overview + N-in-the-name options for N >= 2.
e.g. show2levels, show3levels...
For the sake of completeness/consistency I would suggest having a N=1
variant with that format too. This would duplicate the behaviour of
"overview",
A little progress update.
https://github.com/tecosaur/org-lsp now exists.
I have no idea what I'm doing, so if anyone has feedback on the current
idea, that would be much appreciated.
TEC writes:
> Hi Everyone,
>
> From the Org standardisation effort the idea of using Emacs as
Eric S Fraga writes:
> I wonder whether something like levels:N or show:N or content:N is
> possible in a startup setting, akin to H:N in options?
If I may toss my opinion into the ring, "show:N" seems like the most
intuitive syntax to me :)
--
Timothy
Eric S Fraga writes:
> I wonder whether something like levels:N or show:N or content:N is
> possible in a startup setting, akin to H:N in options?
If I may toss my opinion into the ring, "show:N" seems like the most
intuitive syntax to me :)
--
Timothy
> There are a few touch ups I'll do to my code shortly
I'm pleased to say that I've improved the readability and documentation
of my code (hopefully) in
https://github.com/tecosaur/emacs-config/commit/dc873d3
I hope this may be of some help,
Timothy
Carsten Dominik writes:
> Yes, I mean this code, or something like this, to aid the automatic
> creation of links that are somewhat stable. I have been missing this very
> much.
Hi Carsten, glad to hear that there /does/ seem to be interest in this after
all :)
A few things worth saying I
Tom Gillespie writes:
> Hi Eric,
>Good point, we are indeed missing a line that says "You can mail
> the list directly at mailto:emacs-orgmode@gnu.org.; Here's a patch. I
> assume it is probably ok to put the raw email on the site. Best,
> Tom
Seems sensible :) Thanks for raising this
It's now been 1.5 months, so I'm going to bump this thread.
--
Timothy
TEC writes:
> Bastien writes:
>
>> I'm not an org-plot.el user so I cannot test, but by reading the
>> patches, they look okay.
>>
>> Let's go in "optimistic merging" mode and comm
Hi Sam, link stability is a concern I've had too. I currently have a fix
(or at the very least, an improvement) for this in my config where I
overwrite org-export-get-reference. (see:
https://tecosaur.github.io/emacs-config/config.html#nicer-generated-heading).
I raised this on the list a while
I have 2c on the use of "interpolated".
1. I tend to think of "interpolated" in terms of it's mathematical
meaning
2. The other denotations relate to insertion and renewing, which
simply
doesn't fit.
I appreciate that other people may have used this too, but as I
see it
that just means
Hi Uwe,
Uwe Brauer writes:
I'd rather prefer to have \xout{A} instead of \sout{A}
How can I achieve that?
How about this:
(setcdr (assoc 'strike-through org-latex-text-markup-alist)
"\\xout{%s}")
Hope that helps,
Timothy.
syntax, and it would allow the
fundamental
structure of the table to remain the same -- rows of cells. For
example #+TBLCELLMERGE: @2-3$1 or something like that.
Thoughts?
Tom
On Mon, Nov 2, 2020 at 1:37 PM TEC wrote:
Hi all,
This is a pretty major 'feature request', but I think also
Eric S Fraga writes:
On Tuesday, 3 Nov 2020 at 05:31, Ken Mankoff wrote:
But I'm weary of seeing all my colleagues say "Jupyter" and not
"Org"
+1 (not to mention the case of MSWord instead of Jupyter)
濫
So, yes, if TEC or others can get us there, I'm all for i
David Rogers writes:
IMO this can (and definitely should) be regarded as a purely
cosmetic problem,
to be resolved by purely cosmetic methods. I think the idea that
each table cell
is exactly one unit of information (and can’t be a collection or
array of units
of information) is more
: clearer without line wrapping, more concise examples
definitely
available if I thought about it a tad more)
On Mon, Nov 2, 2020 at 1:37 PM TEC wrote:
Hi all,
This is a pretty major 'feature request', but I think also an
important
one.
When developing large tables, it can often be /necessary
Hi all,
This is a pretty major 'feature request', but I think also an
important
one.
When developing large tables, it can often be /necessary/ to start
using
multi-column/row cells for clarity, and sensible exporting
results.
As far as I am aware, in Org does not currently have any
Hi Everyone,
From the Org standardisation effort the idea of using Emacs as the
basis
of an LSP server for Org has been mentioned a few times.
I thought this deserved it's own thread so here it is :)
I'm quite keen to investigate the viability of this idea.
Some key questions that I think
Russell Adams writes:
On Mon, Nov 02, 2020 at 02:56:58PM +, Eric S Fraga wrote:
(as an aside, Emacs as an LSP could be interesting, especially
if
network based)
LSP is a standard from Microsoft:
https://github.com/Microsoft/language-server-protocol/
It allows networked JSON and
Daniele Nicolodi writes:
On 02/11/2020 10:02, TEC wrote:
I think there are absolutely some benefits for Org users. I am
personally interested in registering Org as an IANA MIME type.
I don't think that registering Org as IANA MIME type will have
the
consequences you hope it has.
Hmmm
Daniele Nicolodi writes:
Acceptance criterion for what? Adoption of what?
It seems to me that some see a the adoption of a simplified
version of
the Org markup language outside Emacs and the org-mode
implementation as
something desirable. However, I don't see what the Org community
would
Dr. Arne Babenhauserheide writes:
Asa Zeren writes:
Also another note is that the worg syntax document does begin
to specify
this. My point is to bring this out into a separate document.
Why should this be in a separate document? The obvious place for
a
standard is worg, and the way
I feel that this also ties into my earlier idea of putting Emacs
as/inside an LSP server for Org. I suspect there may be a a lot
of
potential in making it dead easy to use Emacs as a tool.
I'm rather busy over the next few weeks, but I'd be happy to
spearhead a
project in this direction.
Hi all,
Following what I've read on the list I've developed thoughts on
what the
best approach might be. My current thinking is that it may be
possible
to have Org registered as a standard in such a way that it does
not
constrain our development efforts.
How?
We forgo locking down the
Eric S Fraga writes:
It's not a crazy idea but one which misses one of the best
features of
org mode: it is part of Emacs. For me, a markup language is not
so
exciting: we have plenty of them. What makes org mode powerful
is that
it is infinitely customizable by being part of Emacs. I
Hi Stefan,
This seems very suspicious for one reason. I cannot see "Canvas"
anywhere in the entire codebase of the website, or any loaded
resources.
So I have no idea where on earth the JS you're finding has come
from -
I'm guessing it's improperly injected by a extension. FWIW I also
run
Let's do two at once:
Daniele Nicolodi writes:
Great work! it looks very nice and informative at the same time.
That's the idea! :D
If I can bikeshed a bit more: I like the lighter page background
that is
currently on http://orgomode.org more than the darker one in the
new
version.
Daniele Nicolodi writes:
- (minor) I would add a background to the example in the home
page to
make it stand out more as an example org-mode syntax buffer
- (very minor) why does the example on the home page need to be
an SVG
file? It would be very cool if it could be copy and pasted, but
Hi JRSS, great to hear from you!
JRSS writes:
I've been using org for two years and the new website made me
realize I can maybe help (with the "yes. Do this" link) simply
by joining the email list and help with documentation. I'm not a
coder (baby steps, here and there) but I've been
Eric S Fraga writes:
On Monday, 26 Oct 2020 at 14:54, Daniele Nicolodi wrote:
- (minor) I would add a background to the example in the home
page to
make it stand out more as an example org-mode syntax buffer
This bothered me as well when I visited the site. I think it
would help
to
Daniele Nicolodi writes:
On 26/10/2020 14:54, Daniele Nicolodi wrote:
On 26/10/2020 11:27, TEC wrote:
TEC writes:
there are a few teething issues that have appeared when
deploying the
site on orgmode.org.
These issues have now been fixed! Go wild :P
I've taken the liberty of making
Daniele Nicolodi writes:
I like the new design. Thank you for your work!
Thanks for the kind words!
Two things:
*cough, Three
- in Firefox on a macOS machine, the colophon renders as "Made
with XX
by TEC" with the XX being an Unicode replacement character. What
is it
Nick Dokos writes:
One thing that I have done in the past (and I'm probably not the
onlye
one) on the Emacs SE is refer people to the mailing list through
the
old link: https://orgmode.ord/community.html which does not
exist any
more, so we have a whole lot of broken links on Emacs SE at
gyro funch writes:
The new site looks really great!
Thanks
If we stumble upon minor issues (e.g., typos), what would be the
best
way to notify you?
A quick email works fine for that :) and I'm also happy with
github
issues: https://github.com/tecosaur/orgmode.org/issues/new
All
Leo Vivier writes:
I really like the new design. You’ve done some fantastic work,
Timoty,
as well as all the people who’ve contributed. :)
Thanks for the kind words! It means a lot to hear that the revamp
is
going down well .
I especially like the new page for Tools:
TEC writes:
there are a few teething issues that have appeared when
deploying the
site on orgmode.org.
These issues have now been fixed! Go wild :P
I've taken the liberty of making a post on reddit:
https://www.reddit.com/r/emacs/comments/jic3ww/the_org_website_has_been_revamped/
Once
Hi Everyone, just a quick note from me:
Regarding the intermediate state, there are a few teething issues
that
have appeared when deploying the site on orgmode.org.*
If we could hold off from announcing this on some of the more
high-traffic forums till these get sorted out that would be
thy
>From 3743e507775b446f5f8188958c20f65861fac3fb Mon Sep 17 00:00:00 2001
From: TEC
Date: Wed, 8 Jul 2020 18:34:46 +0800
Subject: [PATCH 01/15] org-plot.el: make indentation method consistent
* lisp/org-plot.el (org-plot/gnuplot): Make indentation consistent, by
replacing a few spaces with tabs.
Only 6 of 347 line
Hi everyone,
In developing my take on the Org website and my coFig file, it has
come
to my attention that there seem to be a few W3C violations in the
HTML
export.
I always export with these settings,
which may affect some of the items below.
#+begin_src emacs-lisp
(setq org-html-doctype
Hi Mirko
Mirko Vukovic writes:
Instead specifying the width, I'd like to use the parameter
\scale.
Have you tried #+attr_latex: :scale SCALE ?
Not sure how you'd put this in a header though I'm afraid - you'll
likely want to change a variable or add an export filter.
Hope something
Hello all,
I'm still hoping that someone might get back to me ... eventually,
so here's another bump.
Timothy.
TEC writes:
Hello everyone. Just in case this has slipped through the cracks
/
fallen under the radar --- here's a little bump.
Timothy.
TEC writes:
Oooops, I've just
1 - 100 of 196 matches
Mail list logo
