Dmitrii Korobeinikov writes:
>> Any chance you could provide a minimal reproducer for
>> your original issue so I can check on my end?
>
> Certainly, save this:
>
> ---cut
> * empty heading
>
>
>
> * another one
>
>
>
> ---cut
On 25/10/20 3:45 pm, Kyle Meyer wrote:
> Michael Gauland writes:
>
>> --start of file--
>>
>> #+LATEX: \setminted{frame=single,framerule=1pt}
>>
>>
>> * Section
>> #+begin_src sh :exports code
>> echo "This is a code block
>> #+end_src
>>
>> --end of file--
>>
>>
>> When I
Michael Gauland writes:
> --start of file--
>
> #+LATEX: \setminted{frame=single,framerule=1pt}
>
>
> * Section
> #+begin_src sh :exports code
> echo "This is a code block
> #+end_src
>
> --end of file--
>
>
> When I export the file to LaTeX, this line is inclued after
>
ian martins writes:
> After making the changes, should I submit updated patches or is it fine to
> push?
Push away. Thanks again.
On 24/10/20 4:00 am, Eric S Fraga wrote:
> On Friday, 23 Oct 2020 at 15:22, Mike Gauland wrote:
>> I have a number of #+LATEX directives at the top of my org file, for
>> configuring the minted package.
> Could you maybe post a minimal example?
>
This file demonstrates the problem, at least on my
Thanks for the feedback. In general, the changes are all intended to be
backwards compatible. Thanks for pointing out changes that weren't.
After making the changes, should I submit updated patches or is it fine to
push?
On Sat, Oct 24, 2020 at 1:05 PM Kyle Meyer wrote:
> Hi ian,
>
> ian
Brilliant! Thanks very much!
-Aaron
On Sat, Oct 24, 2020 at 20:39 Bastien wrote:
> Hi Aaron,
>
> Aaron Madlon-Kay > writes:
>
> > Using the :ruby header arg.
>
> Applied, thanks!
>
> --
> Bastien
>
Bastien writes:
> Hi all,
>
> "Org contrib" refers to the list of Emacs lisp files that you find
> in the contrib/ directory of Org's repository:
>
> https://code.orgmode.org/bzg/org-mode/src/master/contrib
>
> The idea of this directory was to have a place where to promote Org
> packages even
This happened because the new ob-java wasn't based on the old ob-java. I
wrote ob-haxe based on ob-C and ob-python and then derived ob-java from
ob-haxe. I went back and forth about who should be the author of ob-haxe.
I considered listing the authors of ob-C and ob-python, but I thought it
> which Ruby org-mode parser does Github use?
I'm pretty sure that github uses https://github.com/wallyqs/org-ruby.
It is ... not compliant, shall we say. I have making some fixes to the
footnote parsing section on my todo list, but I don't expect to get to
it any time in the near future.
Tom
On 23/09/2020 10:09, Bastien wrote:
> I disagree that a parser is too difficult to maintain because Org is
> a moving target. Org core syntax is not moving anymore, a parser can
> reasonably target it. That's what is done with the Ruby parser, in
> use in this small project called github.com :)
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 commit your patches?
Sounds good then. I don't expect the changes to compromise any
existing
functionality.
Is
Hi ian,
ian martins writes:
>> * Changes
>>
>> - support for functional mode (~:results value~)
>> - accept variables
>> - don't require package, class, and main definitions
>> - write source and result tempfiles to ~org-babel-temporary-directory~,
>> but respects the ~:dir~ header
>> - work
Hi,
Accidentally pressing or on an inactive time stamp in
an org mode buffer, I found myself in an agenda buffer with name "*Org
Agenda(a:2020-10-22)" corresponding to the agenda of the date of the
time stamp.
I understand that this is the expected behaviour (jumping to that date),
but I am
Bastien writes:
> sorry for the delayed answer.
No worries!
> Can you provide a patch against etc/ORG-NEWS announce this?
Attached. Let me know what you think.
Matt
>From 51fb3ef9843ae45884803142f150c5d2f4f4d4c9 Mon Sep 17 00:00:00 2001
From: Matt Huszagh
Date: Sat, 24 Oct 2020 09:36:56
> Any chance you could provide a minimal reproducer for
> your original issue so I can check on my end?
Certainly, save this:
---cut
* empty heading
* another one
---cut end---
Now, when opening this file, you will see:
Hello Bastien,
> Bastien writes:
> Org 9.5 will ship without the packages in the contrib/ directory.
> Emacs lisp files in contrib/ will be packaged as an Org ELPA
Oh no! I hate packages and never use ELPA. :-(
> package that you can install independentely from there. The
On Sat, Oct 24, 2020 at 01:36:05PM +0200, Bastien wrote:
Hi Adam,
this looks good to me, thanks a lot.
Thanks for the review :-)
Does "WIP" means that you want to wait for other patches to complete
this one or shall I apply this one already?
The intention is for it to be a standalone
> On Oct 24, 2020, at 10:40 AM, Bastien wrote:
>
> Palak Mathur writes:
>
>> Yes, it is going to be some work. I will try to get something
>> started and share a draft.
>
> Can you and Leo work together on this ?
>
> Perhaps you can share a first draft (from the user point of view) that
Hi all,
"Org contrib" refers to the list of Emacs lisp files that you find
in the contrib/ directory of Org's repository:
https://code.orgmode.org/bzg/org-mode/src/master/contrib
The idea of this directory was to have a place where to promote Org
packages even if they are not part of Org's core
Palak Mathur writes:
> Yes, it is going to be some work. I will try to get something
> started and share a draft.
Can you and Leo work together on this ?
Perhaps you can share a first draft (from the user point of view) that
Leo can consolidate (from a generic parser point of view) ?
Thanks
Hello,
attached there are a few patches reworking the parsing of org-table
formula mode strings and introducing a new mode flag to enable Calc's
units simplification mode as discussed in a recent thread on the mailing
list. I haven't updated the documentation. I can do it once we agree
that this
Hello,
I have slightly improved the org-table-sum function.
It calls directly calc-eval and yield the same result as vsum.
It can not handle better floating points.
> | 171.00 |
> | 4.07 |
> | 4.44 |
> | 2.61 |
> | 12.21 |
> | 6.69 |
> | 19.72 |
> | 23.09 |
> | 6.23 |
> | 15.28 |
>
Hi Leo,
Leo Vivier writes:
> Bastien writes:
>
>> Sorry, perhaps I was not clear: (1) and (2) do not need to be separate
>> documents.
>
> No, you were quite clear. I just surmised that two documents would be
> required, but upon thinking about it some more, (1) and (2) would make
> for a
Sent from my iPhone
> On Oct 24, 2020, at 7:50 AM, Bastien wrote:
>
> Hi Palak,
>
> Palak Mathur writes:
>
>> I am fairly new to Org. Let me see if I can use it as a markup in an
>> Editor other than Emacs. I will report on what syntax options are very
>> Emacs specific, what are general
Hi Jack,
Jack Kamm writes:
> Thanks Bastien, the Woof! tool looks interesting.
Thanks! I'm working on a small woof.el package to make it more
useful for both maintainers (setting headers) and users (checking
upcoming changes or help requests).
> By the way, on seeing this thread again, I
Hi all,
I've updated https://orgmode.org/worg/org-maintenance.html to clarify
a few points:
- we don't have a release schedule;
- after Org 9.5, x.y versions like 9.6, 9.7, etc. will be *minor
versions*, not major versions. So the next major after 9.5 is 10.
- we don't follow semantic
Thanks Bastien, the Woof! tool looks interesting.
By the way, on seeing this thread again, I realized this patch probably should
have been applied to the maint branch. So I've cherry picked it into there, and
merged back into master.
Bastien writes:
> Hi Jack and Adrian,
>
> Jack Kamm
Hi Bastien,
I tried to figure out what you mean by that but I am drawing a blank.
I completely deleted my emacs folder and then did
=package-list-packages= and installed =org-plus-contrib= restarted
emacs and the problem showed up, while it wasn't there before.
How can I see the individual
Bastien writes:
> Sorry, perhaps I was not clear: (1) and (2) do not need to be separate
> documents.
No, you were quite clear. I just surmised that two documents would be
required, but upon thinking about it some more, (1) and (2) would make
for a cohesive whole.
> Great, thanks for
Hi Leo,
Leo Vivier writes:
> Bastien writes:
>
>> As the first paragraph says:
>>
>> "This document describes and comments Org syntax as it is currently
>> read by its parser (Org Elements)"
>>
>> while we need a description of Org's syntax from the point of view of
>> (1) a human writer
Hi there,
Bastien writes:
> As the first paragraph says:
>
> "This document describes and comments Org syntax as it is currently
> read by its parser (Org Elements)"
>
> while we need a description of Org's syntax from the point of view of
> (1) a human writer and (2) any possible Org
Hi Palak,
Palak Mathur writes:
> I am fairly new to Org. Let me see if I can use it as a markup in an
> Editor other than Emacs. I will report on what syntax options are very
> Emacs specific, what are general and what can be ported.
Thanks! I think it is less a matter of *what* is described
Hi Matt,
sorry for the delayed answer.
Matt Huszagh writes:
> Bastien writes:
>
>> Prefer
>>
>> * lisp/ob-latex.el (org-babel-latex-preamble): New option for LaTeX
>> preamble customization.
>>
>> "New option" is quite standard, an "option" being a customizable
>> variable. In this case,
> On Oct 24, 2020, at 7:09 AM, Bastien wrote:
>
> Hi Wes,
>
> Wes Hardaker writes:
>
>> Ok, I'll try to create a template we can fill out in github next week
>> (I'm swamped this week with a deadline).
>
> If you manage to make any progress on this, please share it with the
> whole list
Hi Protesilaos,
sorry for the delay in replying.
Protesilaos Stavrou writes:
> Please see the attached diff. An explanation is offered below.
This looks good to me -- is this enhancement compatible with older
versions of Emacs? I'd like to keep Org compatible with Emacs 25.
If so, can you
Hi Anthony,
Anthony Carrico writes:
> * ox-publish.el (org-publish-sitemap): Include files that have an
> ancestor below base-directory with no published files and sitemap style
> is tree.
thanks for the patch and sorry for the delay in replying. I'm not
sure I understand the bug it fixes:
Hi Ferdinand,
Ferdinand Pieper writes:
> When passing a remote file like "/ssh:myserver:/myfile.txt" to a
> gnuplot block as variable the gnuplot process can not access the
> remote data.
Applied, thanks!
> An example:
>
> #+begin_src gnuplot :var data="/ssh:myserver:/myfile.txt"
> plot data
Hi Wes,
Wes Hardaker writes:
> Ok, I'll try to create a template we can fill out in github next week
> (I'm swamped this week with a deadline).
If you manage to make any progress on this, please share it with the
whole list so that interested people can possibly follow.
For the record, I
Hi David,
David Masterson writes:
> Just wondering -- what's the limit in the number of tags for a headline?
> What if I have a headline with lots of tags or some very long tags?
Please try and let us know what happens :)
--
Bastien
Hi Kyle and Morgan,
Kyle Meyer writes:
> morgan.j.sm...@outlook.com writes:
>
>> From: Morgan Smith
>>
>> * lisp/org.el (org-check-before-invisible-edit): Fix a docstring typo.
>> ---
>>
>> Hello Org! This is my first patch so go easy on me. I'm planning on
>> doing more patches in the future.
Hi Ian,
feel free to install the patch when you think it's ready.
One minor nitpick:
-;; Author: Eric Schulte
-;; Maintainer: Ian Martins
+;; Author: Ian Martins
I suggest you leave Eric Schulte as the author while adding yourself
as the maintainer, even if the "change" is a big rewrite.
Hi Jack and Adrian,
Jack Kamm writes:
> Adrian Kummerländer writes:
>
>> I noticed that after updating to Org 9.4 many of my Python-based Org
>> files fail to execute with various `io.TextIOWrapper' related error
>> messages. The reason for this is that opening the exec tmpfile as `f'
>>
Hi Protesilaos,
Protesilaos Stavrou writes:
> The export dispatcher's active keys are highlighted using the
> 'org-warning' face. That face is applied in various contexts, including
> the agenda.
>
> Users who have difficulty reading the active keys of the export
> dispatcher are therefore
Hi Neil,
Neil Cherry writes:
> I'm on a Windows 10 System, I'm using ob-sql.el and when I C-c C-c
> on the src block I get:
What version of Org are you using? M-x org-version RET
Thanks,
--
Bastien
Hi Aaron,
Aaron Madlon-Kay writes:
> Using the :ruby header arg.
Applied, thanks!
--
Bastien
Hi Adam,
this looks good to me, thanks a lot.
Does "WIP" means that you want to wait for other patches to complete
this one or shall I apply this one already?
Best,
--
Bastien
Applied, thanks!
--
Bastien
Hi Timothy,
TEC writes:
> I'm still hoping that someone might get back to me ... eventually,
> so here's another bump.
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 commit your patches?
Is
Hi Timothy,
TEC writes:
> 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.
thanks for the careful tests and for reporting this.
> I always export with these settings,
> which may affect
Hi Georgios,
Georgios Bakirtzis writes:
> Org without contrib does not have the following issue.
what part of your configuration loads contrib packages?
Can you bisect and find what contributed package triggers the error
you have?
Thanks,
--
Bastien
51 matches
Mail list logo
