Hi Matthew,
not sure I replied to this one but in case I didn't, yes, my initial
fix was wrong, I reverted it.
Thanks!
--
Bastien
D writes:
> Thank you in advance,
PS: I don't use org-superstar-mode (yet) so I can't really answer
your questions, but I hope others will do.
--
Bastien
Hi Texas,
Texas Cyberthal writes:
> Why does there need to be an Org version of mixed-pitch-mode? It
> already works for Org.
Yes, indeed.
PS: Speaking of good defaults, I think quoting emails with ">"
instead of #+begin_quote is way more readable.
--
Bastien
Hi Victor,
thanks for reporting this, this is fixed now in the maint branch.
Best,
--
Bastien
#+begin_quote Bastien
> Having said that, if Org could have a simple org-mixed-pitch-mode, or
> something like that, that could be very helpful, since it could make
> such configuration much easier.
If anyone wants to start coding something like this, we can consider
referencing it on Worg.
Hi Bruce,
> * Bug Report
>
> (setq org-cycle-include-plain-lists 'integrate)
>
> seems to have no effect.
Thanks for reporting this. Fixed now. This was the consequence of
this commit: https://code.orgmode.org/bzg/org-mode/commit/c2aebcee27
Best,
--
Bastien
Hi Stardiviner,
stardiviner writes:
> This this related to recently new added option value.
the option was introduced just 2-3 hours before Bruce reported his
problem ;)
> #+begin_src emacs-lisp
> (setq org-adapt-indentation 'headline-data)
> #+end_src
>
> It is introduced in commit
This this related to recently new added option value.
#+begin_src emacs-lisp
(setq org-adapt-indentation 'headline-data)
#+end_src
It is introduced in commit "e3b79ad2bf7ab7b91c0ad2b8383d639bfe154ce7". Which
might breaks indentation of plain list etc.
Bruce Tulloch writes:
> * Bug Report
>
You should try ~:results value html~. Here is what I got correctly:
#+begin_src R :results value html
library(xtable)
x <- rnorm(100)
y <- x + rnorm(100)
print(xtable(summary(lm(y ~ x))),type="html")
#+end_src
#+RESULTS[<2020-02-11 13:14:59> 91ff0df2529284897e3585e3ec2e640290ee8308]:
Bastien writes:
> Hi Stardiviner,
>
> I fixed this in master, thanks for reporting this bug.
>
> Best,
Thanks Bastien, You're very active recently. I saw you fixed lot of issues and
new patches. Thanks, really.
--
[ stardiviner ]
I try to make every word tell the meaning what I want
I am having trouble understanding how short captions are supposed to work.
Consider this org document:
#+begin_src org
,#+title: Short Caption Test
,#+author: Org User
,#+label: table1
,#+caption[This is table1]: And here go on at length in a longer caption.
| Name | Favorite Number |
Hi Tyler,
Tyler Smith writes:
>
> What happend to org-man? I think the file was deleted from org mode, but
> I don't see any explanation in the news file. I think this qualifies as
> an incompatible change, at least for those of us that used org-man?
The prefix for all the link-related
Hi,
What happend to org-man? I think the file was deleted from org mode, but
I don't see any explanation in the news file. I think this qualifies as
an incompatible change, at least for those of us that used org-man?
Best,
Tyler
--
Tyler Smith
http://plantarum.ca
> Micro$loth WindBlows is a computer virus
Well that's mature and appropriate.
I recently did an implementation of `ob-pwsh` for supporting powershell
core (it assumes there’s a pwsh command available on PATH though thats
configurable with `org-babel-command:pws`). Here’s the link
Hi Klaus,
MS Window writes:
> There is no explanation there I should put the configuration. The org-babel
> documentation is too brief for me as beginner to understand.
First, save that file somewhere. Then, in your emacs config, add the
directory containing ob-powershell.el to the
Micro$loth WindBlows is a computer virus
But if you must use Windows, suggest you use Cygwin and BASH and/or EShell
{the Emacs Shell}--you can do much more than PowerSh3ll
And Emacs & OrgMode work very nicely on Cygwin
On Mon, Feb 10, 2020 at 11:58 AM MS Window wrote:
> Hello,
>
> can you
Hi Yuan Lin,
thanks for reporting this.
Yes, this is because of the recent addition you are referring to,
which I find a bit problematic, even though I understand the intent.
It is good to be able to navigate the agenda commands dispatch window
but losing the SPC key is too high a price for
On 2/10/20, Bastien wrote:
> Hi Samuel,
>
> thanks for your feedback.
>
> Samuel Wales writes:
>
>> obviously, as a default not indenting text as you seem to propose is
>> good for newcomers.
that statement was in the context of accessibility.
>
> Perhaps, we will see!
indeed we will get
Hi Adam,
Adam Porter writes:
> I've pushed a new feature to org-ql's master branch: a Magit-like view
> dispatcher using Jonas Bernoulli's transient.el library.
It looks really neat!
I wish we could unify at the two main Org dispatch screens, i.e. org
export and org capture selection
Samuel Wales writes:
> nil has always worked for me. i didn't think a new feature was
> necessary, but i am curious. what does your change do?
(See the other message I just sent for a quick explanation.)
--
Bastien
Hi Samuel,
thanks for your feedback.
Samuel Wales writes:
> obviously, as a default not indenting text as you seem to propose is
> good for newcomers.
Perhaps, we will see!
> as for org as it is now, with a mixture of at least 3 indentation
> styles in the wild, idk.
What I observed is that
i think this is a really good idea.
there are subtleties including:
- list bullets (fixed is good for aligning succeeding lines)
- timestamps (many align these informally or in headers)
- numbers (many align these informally -- but .,-+'?)
- todo kw (defined by user, would be fantastic
[this is addressed to bastien]
hi,
if you are thinking of changing the default to indenting meta lines
and asking for opinions on that:
fwiw, if org /were starting out/, i would propose that meta stuff not
be indented at all either. then the regexps everywhere could be
reliable. and it
hi bastien,
i deeply apologize. that statement was not clear. as much as
possible i will be more clear in the future. i appreciate your
looking into it.
nil has always worked for me. i didn't think a new feature was
necessary, but i am curious. what does your change do?
samuel
Bastien writes:
> Hi Eric,
>
> Eric Abrahamsen writes:
>
>> I ended up writing a function on top of that that does find-or-create,
>> so you can go to a certain outline path, creating and inserting
>> (optionally in sorted order) the missing segments as you go. It was
>> fairly difficult to get
Hello,
can you help me ? I want to use org-babel for Powershell scripting. I found
this code chunk on the internet for customizing org-babel for Powershell on
github:
https://gist.github.com/cbilson/ae0d90d163be4d769f8a15ddb58292bc
There is no explanation there I should put the configuration.
Hi friends,
I've pushed a new feature to org-ql's master branch: a Magit-like view
dispatcher using Jonas Bernoulli's transient.el library. It makes for
quick and easy modification of org-ql-view queries, allowing you to
build them interactively rather than requiring you to write Lisp code or
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Hi!
In ob-lilypond the variable org-babel-lilypond-commands appears to
be in a weird state. The customize interface says:
org-babel-lilypond-commands: nil
> [ State ]: UNKNOWN, you should not see this.
> Commands to run lilypond and view or play the results.
> These should be
>> The problem now is that removing support for 'elisp' would break too
>> much.
>
> What I suggest for this particular issue is this: first be liberal
> while staying consistent (thus allowing "elisp" as Troy suggest),
> then be strict when a major release is issued (thus removing aliases
> that
30 matches
Mail list logo
