Adam Spiers writes:
> Fix a -Wimplicit-int compiler warning, and make it more obvious how to
> obtain scrnsaver.h on three of the most popular Linux distros.
Thanks, sounds good.
Note that commits in the Org repo typically follow the Emacs convention
of including a changelog-like entry. But
吴锐扬 writes:
> The author explained his motivation for the commit in the mailing list before
> it got applied:
>
>> That's because lob calls get wrapped internally in an anonymous
>> emacs-lisp source block that then feeds through the result from the
>> actual call as elisp. The attached patch
Gustav Wikström writes:
> Hi,
>
> This may be a stupid question but I didn't find anything conclusive in
> the manual or online after a (albeit fairly quick) scan.
>
> Is there currently a way to declare that property drawers (and the
> file level property drawer in particular) should be hidden
Michaël Cadilhac writes:
> My problem wasn't at all, as you point out, that the tag would erase the
> entry.
>
> It has to do with habits: The habit graph overwrites anything else. I
> like having org-agenda-tags-column to a low value (wide screen), but
> tags are crucial to my workflow, so
Michael Heerdegen writes:
> Do you know whether I can assume that one of those is always present
> (org-marker probably, since org-hd-marker is not always present) when
> examining the result of `org-agenda-get-day-entries'? I don't care
> about the exact location in an entry.
Going through
ian martins writes:
> Subject: [PATCH] ob-java.el: Change the default back to scripting mode
>
> * lisp/ob-java.el: Change the default to scripting mode. Add name to
> authors.
The changelog entry should explicitly list the variables/functions that
are modified. So in this case
*
The author explained his motivation for the commit in the mailing list before
it got applied:
> That's because lob calls get wrapped internally in an anonymous
> emacs-lisp source block that then feeds through the result from the
> actual call as elisp. The attached patch should suppress the
>
The attached patch adds a "project" option for org-link-file-path-type.
When this is set, links to files under the current project root will be
relative, while links elsewhere are absolute.
It relies on project.el, which appears to have been added in emacs 25. I
used fboundp to check whether the
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
Hi.
Thanks for your great work and the wonderful new page!
A minor detail: I use the plugin "Decentraleyes" and with this
activated there is quite a bit JavaScript garbage at the end of the
page (below the "Created by" footer). The part below the footer is
this:
#+begin_src js
{ const iframes =
FWIW, it doesn't seem like an accident. You might ping the author of this
commit:
$ git log -S "(let (org-confirm-babel-evaluate)"
commit 56bf3d789146fcd3c9f82d875de28c394fe593a0
Author: Achim Gratz
Date: Wed Apr 10 20:28:31 2013 +0200
Babel: avoid superfluous confirmation for internal
On 28/10/2020 17:59, TEC wrote:
>
> 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
I wrote:
> With diary, I can use arbitrary Lisp expressions to generate dates, and
> those expressions can also return a string to use as non-nil return
> value to generate non-constant headlines including certain numbers for
> example. [...]
My solution so far: I've set up my
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.
Wow! I'm a big fan of the subtle checkered background and reduced
"Created by" bar, along with the changed background of the top menu bar;
it makes the homepage much easier on the eyes. The example org-mode file
with commentary is a big improvement for letting new folks know how a
file is laid
On 2020-10-28 at 08:40 -07, Daniele Nicolodi wrote...
> 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.
A few more minor comments based on the current version at
On 28/10/2020 13:25, TEC wrote:
>
> 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
That's OK - some more searching and I believe I found the info I was asking
for: https://orgmode.org/worg/org-maintenance.html
Thanks anyway.
Rob
—
Rob Davenport
Consulting R Engineer
ABB Cleveland
“Don’t look the other way. Make good architecture happen.”
-Original Message-
From:
Great, thanks, That was it. It never occured to me that it's not
begin_src that I wanted, I just tried to tweak that one.
So, indeed: #+begin_export markdown etc. is exactly what I need.
Thanks again.
Martin
> "Julius" == Julius Dittmar writes:
Julius> Hi Martin,
Julius> if I
Hi Martin,
if I understand correctly, you do not want to have a section that quotes
source code, but literal source code.
As far as I understand, that means using
#+begin_export markdown
...
#+end_export
block, not
#+begin_src markdown
...
#+end_src
block. That block will then be ignored in any
Hello Jack,
> Thanks for volunteering to maintain ob-R.el :)
Thanks for the encouragements and the suggestions.
I need will take some time to dive into the existing code but
I will definitely look into it and keep you posted.
I've also noticed a [1] bug waiting to be fixed.
[1]
Immanuel,
my take
> - Not possible to tangle all code going to a specified file
i'm not sure what this means.
> - Not possible to add line directives without major surgery
yes, that would be a problem (... if i were programming in,
e.g., C, etc., so *is* for other people).
> - Not all
Hi Jeremie,
Thanks for volunteering to maintain ob-R.el :)
I'm bumping this patch [0] to see if it could be merged into ob-R.el. It
fixes some long-standing issues with prompt mangling for :session blocks
with :results output.
Elsewhere in the thread, Chuck had a suggestion [1] to allow
Hi,
I have troubles to export (or publish) some orgfiles, which contain
``src'' snippets intended for markdown. The (for me) unwelcome behavior
is the same for org-export and org-publish, I guess, since it has the
same core reason.
The problem currently for me is for the markdown format. I
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
On Wednesday, 14 Oct 2020 at 16:18, 吴锐扬 wrote:
> I have org-confirm-babel-evaluate set to t by default. With this, I
> expect to be queried with the execution of every code block or lob
> call. However, this does not happen when exporting lob calls (to latex
> for example). Here is an example:
I see, contribution is sure fine.
[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/
On Wed, Oct 28, 2020 at 4:55 PM
Hi,
This may be a stupid question but I didn't find anything conclusive in the
manual or online after a (albeit fairly quick) scan.
Is there currently a way to declare that property drawers (and the file level
property drawer in particular) should be hidden when opening a new Org file, no
ian martins writes:
> But I want to follow your conventions. I will put the authors of ob-C
> and ob-python (Eric Schulte and Dan Davison) as the authors of
> ob-java and ob-haxe. The implementations are nearly the same. it
> wouldn't make sense for them to have different authors.
Thanks for
Hi Ken,
Ken Mankoff writes:
> I'll help maintain ob-screen.el
Thanks!
I added your name as the ob-screen.el maintainer in commit b499b0827.
Best,
--
Bastien
Hi stardiviner,
stardiviner writes:
> I would like to be a maintainer of ob-clojure.el too.
For now, I'd rather have one maintainer per file than several.
Contributions are always welcome, of course. If I don't have time to
maintain ob-clojure.el correctly next year, I'll ask for someone
Hi Stardiviner,
stardiviner writes:
> I searched my name in maintainer line.
>
> Here is the complete list:
> ```
> File: lisp/ob-eshell.el
> 5 25 ;; Author: stardiviner
I added yourself as the maintainer for ob-eshell.el (commit 1d105a429),
thanks.
My call for ob-* maintainers for Org's
I think the org way of tangling just doesn't work well for compiled languages.
Here are some reasons:
- Not possible to tangle all code going to a specified file
- Not possible to add line directives without major surgery
- Not all language modes do the correct thing
- No way to prevent
Hello,
I an mot sure if this is a bug or "feature".
1. emacs -Q (using emacs-28.0.50, org-version 9.3)
2. C-x C-f test.org (new file)
3. Enter * Test (A new heading is created with name Test)
4. M-x org-id-get-create
5. M-x org-id-update-id-locations
Echo buffer: "1 files scanned, 1 files
34 matches
Mail list logo
