with the coderef (i.e. coderef prefix), the
other is the addition of header arguments that provide the same
functionality as switches. Best,
Tom
> This is already conflating the two. I'd like to solve the issue at hand
> without having header args interfere at all.
>
> This can happen
Missed removing a debug message. Here is the correct patch. Best,
Tom
On Sun, Apr 4, 2021 at 10:22 PM Tom Gillespie wrote:
>
> Hi Nicolas,
>I've attached a patch with a first pass implementation that I think
> resolves most of the issues. It probably needs a few tests
with the cost of having to pull out :coderef-prefix in a number of separate
contexts. Best,
Tom
> If possible, I'd like not to conflate current issue with switches
> deprecation, which needs to be discussed separately.
We can decouple them, so not an issue. The attached patch implements
the
on a basic implementation and will respond in this
thread again when I have something worth looking at. Best!
Tom
For the record there are at least 3 different inconsistent regex
that are used to detect coderefs.
org-element:
(string-match "-l +\"\\([^\"\n]+\\)\"" switches)
and
feedback would be greatly appreciated. Best!
Tom
1. https://github.com/tgbugs/laundry
2. https://docs.racket-lang.org/brag/#%28part._.The_language%29
3. https://github.com/tgbugs/laundry/blob/master/org-mode/parser.rkt
t at least it can be specified in the file. In
general adding a token that duplicates the function of an existing
token is a bad idea. For a similar reason mixed delimiters cannot be
allowed, they make the grammar completely ambiguous. Best,
Tom
, though
ISO8601 interval
specification might be an option. Similarly there are extensions for
dealing with uncertain dates and times, but I don't have good
proposals for those right now,
and the use cases are also somewhat out of scope.
Best,
Tom
Reposting my reply to the emacs-devel thread here as well. The hack I
mention that has performance issues was derived from John's solution
for the <> issue (though the performance issues are all of my own
creation). Best,
Tom
This is a known issue with org babel blocks. It is due to th
in the interaction between
tables and #+macro: commands containing the pipe character that
org-export implements incorrectly). Relatively speaking, the potential
approaches discussed in Timothy's previous proposal are much more
likely to be tractable. Best,
Tom
You should be able to run C-c C-c on #+property: directives before the
first headline and they will be updated without reloading the buffer.
Best,
Tom
Not 100% sure about this, but take a look at the hs-set-up-overlay
variable, it seems like it might be possible to customize that to
achieve this behavior. Best,
Tom
It is built into the core org distribution.
probably be to
decorate org-bable-insert-result (in ob-core.el) to detect the size of
the result and write the full result to a separate buffer if it is
beyond the limit you set. Best,
Tom
https://github.com/nobiot/org-transclusion
this exactly. You might also be able to wire up
org-protocol to the X clipboard (if you are on linux).
Best,
Tom
without quoting it. I'm not sure about the best
way to fix this. It seems to me that the call to regexp-quote should
be removed but I'm not entirely sure of the consequences of doing
that. Thoughts? Best,
Tom
PS While on the topic of coderefs, let me drop a note that is a
preview of some
gt; (anyway, good luck with that, even with any significant subset of that!)
Thanks, and thanks for the inspiration!
Tom
set to true
and putting the leading spaces in the file (instead of doing whatever it is
that doom does by default) induces significant complexity into the
implementation. I would love to see it gone, as I'm sure anyone wanting
to parse org files in future will too.
Best!
Tom
if
that functionality was removed. It would be great if we could find
some examples of org files or users that use the tabels.el
functionality so we can understand what org tables are missing. Best,
Tom
still add metadata without having to modify the files. This
would vastly simplify some of my documentation generation code where I
modify the first section of a bunch of org files as I process them
rather than modifying the config. Thanks!
Tom
to be handled more sanely with #+html_head:. Am
I missing something? Best,
Tom
To hop in on the hypothes.is thread. I have spent quite a bit of time
working with hypothes.is and related tooling (mostly in python), so
here is a brain dump on interactions between org and hypothes.is. As
others have mentioned, this could easily be its own thread. Best!
Tom
A quick note
See also. https://lists.gnu.org/archive/html/emacs-devel/2017-04/msg00798.html
and
https://www.reddit.com/r/emacs/comments/696pv1/rms_supports_language_server_protocol_integration/
for some discussion. Best,
Tom
On Mon, Dec 14, 2020 at 4:31 PM Tim Cross wrote:
>
>
>
> I am no fan
up in case sql-postgres-program is
somehow nil seems reasonable. Best,
Tom
/unpackaged.el#export-to-html-with-useful-anchors.
Best!
Tom
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
From 490c48a9750d04571e63250208ae90b2cd85 Mon Sep 17 00:00:00 2001
From
, but absent such an implementation it would be up to the user
to figure out the semantics for each of the languages they wanted to
evaluate directly. Best,
Tom
This is caused by elastic-indent-mode. As foretold
https://lists.gnu.org/archive/html/emacs-orgmode/2020-11/msg00325.html.
Tom
On Mon, Nov 30, 2020 at 1:38 PM Titus von der Malsburg
wrote:
>
>
> On 2020-11-30 Mon 19:25, Diego Zamboni wrote:
> >>
> >> I’m aware of sever
ive in
custom-file. I'm not sure what would happen if the old definitions
were still in .emacs, regardless, a good time to make a backup of
.emacs just in case. Best,
Tom
/Adding-Hyperlink-Types.html that would do
the type setting for you. If you want those definitions to live in the
org file you could use Eric's eval: (org-sbe startup) local variable
approach to ensure that the elisp definitions are always available.
Best,
Tom
The example from the quickstart:
#+MACRO
pulate org-agenda-files by scanning folders
for existing org files and then having a blacklist to exclude files I
do not want.
Best,
Tom
some-folder followed by a block rm contents/ -r getting reordered),
there are major downsides to trying to guess how to concatenate
multiple blocks and trying to specify restrictions on where and how
using the same name is allowed or can be safely used is not something
that anyone would want to try to do. Best!
Tom
> As there is the option ! to "apply local variables and permanently
> mark these values" but there is no option "not to apply local
> variables and permanently mark these values".
I have a longer reply that I will send tomorrow, but wanted to respond
to this.
Yes exactly! I have the equivalent
hings
like org-babel in the core. Fortunately the community has long
experience with these kinds of limited perspectives and knows how to
deal with them, but they cannot simply be ignored.
Best,
Tom
internal notes. Can I add it as a new
section? Best!
Tom
On Wed, Nov 25, 2020 at 2:06 AM Tim Cross wrote:
>
>
> ian martins writes:
>
> > Something I've found challenging is the inconsistency between babel
> > languages. It makes it difficult for a babel user to get a sou
that needs to be fixed. I have been working on writing up
and diagraming a potential solution for community feedback, but it is
not quite ready yet. Thus, I'm filing this thread along with the
others that I have been compiling about org babel issues. Best!
Tom
On Tue, Nov 24, 2020 at 6:40 PM Tim
like that which
blindly executes an org babel block should never be permanently
accepted
Best,
Tom
variable and set that
from a buffer local variable for the local additions to PYTHONPATH
along with getenv PYTHONPATH. A working example below. Best!
Tom
#+name: orgstrap
#+begin_src elisp :results none :noweb noexport
(defvar-local local-python-path nil)
(defun advise--obe-python-path (command
I have read many perspectives like this of late on this mailing list.
In summary I think that Org is such an incredibly flexible and
powerful tool that many users have not the faintest idea what other
users are doing with it (for example I am completely mystified by the
level of activity in the
spoken up to point out
that it would likely not be a welcome change, as this thread shows. The
good news is that all is not lost and now when users want electric-indent-mode
in org it will be consistent with upstream.
Best,
Tom
> > Ugh, I update my emacs package pretty infrequently and I usually have 30 or
> > more packages updating at a time -- I can't see wading through 30 NEWS
> > files searching for landmines...
> >
>
> Yes, this I think is a problem. Most of those packages probably only
> have minor changes and bug
org could benefit from more
extensive testing coverage. There was a change between 9.1 and 9.3 that
completely broke org babel edit src functionality because it did not
correctly restore the window layout on exit. Now we just need to find
people willing to write the tests in addition to notifying the mailing list :D.
Best,
Tom
EWS files
> searching for landmines...
>
>
> -- Bill
>
>
> On Mon, Nov 16, 2020 at 9:10 PM Tom Gillespie wrote:
>>
>> Semver is unlikely to help because the question is what is "broken" by
>> a change in version. Semver would likely be about breaki
ack where we
are now -- to know what really changed you have to read the NEWS.
Bastien has also talked about hear-ye versioning, which says when a
version changes users need to read the news. Best,
Tom
On Mon, Nov 16, 2020 at 1:15 PM gyro funch wrote:
>
> On 11/16/2020 9:26 AM, Tom Gillespie wrote:
Here is a patch that might serve for the purpose. Best,
Tom
On Mon, Nov 16, 2020 at 5:47 AM Russell Adams wrote:
>
> https://orgmode.org/community.html
>
> This really needs to state that the Org-mode mailing list is
> subscriber only. Membership is open, but that users should su
. The workflow during development would be
to account for any change to defaults in those functions. Thoughts?
Tom
as well
https://gitlab.com/gitlab-org/gitlab-foss/-/blob/master/Gemfile#L156.
They may be easier to reach out to. I have also cced Wally to see if
he has any insights here. Best!
Tom
l-evaluate and take a function as an argument, ask if t, don't
ask if nil, or ask only if result is t (or was it nil ... regardless match
org-confirm-babel-evaluate). org-confirm-closure-evaluate maybe? (Again if
this already exists, then woo!).
Best!
Tom
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 an
> important
> one.
>
> When developing large tables, it can often
ors, not standardization.
A few more thoughts in line. Best!
Tom
On Sat, Oct 31, 2020 at 8:22 PM Asa Zeren wrote:
> this is impossible. If org catches on before it is standardized, we
> end up in the situation of Markdown, with many competing standards and
> non-standards. Hence, standardization
to standardize.
Best!
Tom
define how to consume quoted elisp lists without
raising errors. That said, I'm not sure that org babel requires that
ob-lang implementations handle this. Maybe it should? I've added this
to my growing list of issues related to org babel regularization.
Best!
Tom
On Thu, Oct 29, 2020 at 7:25 AM James Bo
Even if this did work for plain lists it won't work for headlines
because headlines have an arbitrary number of stars and thus it is not
possible for the grammar to know what is a sub-headline vs "the next
headline". For a similar reason I'm fairly sure that the sublist
approach will not work due
the grammar. More in line. Best!
Tom
> Do you need to? This is valid as an entire Org file, I think:
>
> *** foo
> * bar
> * baz
>
> And that can be represented in EBNF. I'm not aware of places where behavior
> is indent-level specific, except inline tasks
The image is a bit off center no?
On Mon, Oct 26, 2020 at 1:27 PM TEC wrote:
>
>
> 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
identify things
that are block start lines and block end lines, but you need stacks to
keep track of heading level, indentation, plain list level, and block
name. I might be missing a few other places where stacks are required,
but those are the big ones. Best,
Tom
On Mon, Oct 26, 2020 at 12:48 PM Ken
> 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
, top level and
nested code had semantics that were as close to each other as possible
(and it shows).
Best!
Tom
A vote for A from me. I think that using the light background for the
section above the fold fits better with the color themes of the other
pages and will make the transition less jarring. Best!
Tom
On Thu, Sep 24, 2020 at 9:20 AM TEC wrote:
>
>
> An update.
>
> 1. We h
though I guess you never know). Thank you
for tracking this down, and now I know how to add ert tests for things
like this in the future! Best,
Tom
On Tue, Sep 15, 2020 at 12:21 AM Kyle Meyer wrote:
>
> Tom Gillespie writes:
>
> > Hi,
> >The 9.4 release has a bug where it
Hi,
The 9.4 release has a bug where it will only tangle the first noweb
reference on a line.
This is also present at 9c31cba002a1ba93053aebea1f778be87f61ba06. It happens in
emacs-27 and emacs-28. The reproduction is below. Best!
Tom
The expected content of oops-3.el should be 1 2 1
be implemented
as default behavior. I have a long email that touches on these issues
in the works for after the 9.4 release, so thank you for providing an
excellent example. It seems like one possible solution for your
workflow would be to advise org-babel-expand-src-block to insert the
shebang. Best,
Tom
Hi Matt,
Looking good here. Thanks!
Tom
On Wed, Sep 9, 2020 at 12:06 PM Matt Huszagh wrote:
>
> Tom Gillespie writes:
>
> > [...] I have a number of use
> > cases that I can imagine would benefit greatly from being able to
> > define a :header-args: :header
Great, thank you. Also handy to see the "right" way to traverse up the
tree. Best!
Tom
On Sun, Sep 6, 2020 at 9:52 PM Bastien wrote:
>
> Thanks Tom for the feedback.
>
> >> - org-babel-exp-process-buffer
> > Yes
> >> - org-babel-ref-resolve
>
in the data
model together. Best,
Tom
On Mon, Sep 7, 2020 at 11:17 AM TEC wrote:
>
>
> Hi all,
>
> I've taken a little look at improving how Org is seen/searched around
> the web. We currently have open graph and twitter meta tags, and I've
> now see that we should be able to improve
idea. I wonder what other perspectives there are on this. Best!
Tom
On Sun, Sep 6, 2020 at 2:37 AM Bastien wrote:
> - org-babel-exp-process-buffer
Yes
> - org-babel-ref-resolve
Probably not?
> - org-babel-expand-noweb-references
Probably not?
for getting this in! Best,
Tom
On Sat, Sep 5, 2020 at 8:45 PM Kyle Meyer wrote:
>
> Tom Gillespie writes:
>
> > Hi Kyle,
> > Following up in this thread having investigated the impact of coderefs.
> > My conclusion is that coderefs need to be stripped out before they are
>
number of blocks using :dir and on host a
it needs to be /home/my-usual-user-name/working/ and on another it has
to be /home/my-other-user-name/working/ because I wasn't the first
user named tom to get an account on that system. Similar use case
would be switching the database port based on which host I
ng mail on org-babel, which I might hold off on
until after the 9.4 release).
Best!
Tom
On Fri, Sep 4, 2020 at 8:37 AM Bastien wrote:
> Let's continue to discuss this for after 9.4.
have been superseded by the headers on a block then that
is incorrect and they should not be evaluated until it is clear that
they are the value of the header for that block and have not been
superseded.
Best!
Tom
:host:/path/to/file")
The implementation of unless-archived is below along with a demo org file.
Best!
Tom
* Bootstrap
This is a giant hack which only works because the state of Emacs
when resolving the tangle header is sitting on the block in question
which I'm guessing is an implementat
included a patch against maint that reuses the let block
from org-babel-execute-src-block to accomplish this.
Best!
Tom
From dfb8eee9901a0fe4bd933911386f69863785a15b Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Fri, 4 Sep 2020 20:35:03 -0700
Subject: [PATCH] lisp/ob-core.el: org-babel-check
,
Tom
On Tue, Sep 1, 2020 at 11:07 AM Tom Gillespie wrote:
>
> Hi Timothy,
> Thank you for all your work on this! A couple of suggestions. When
> the dimensions of the browser window become too narrow the links in
> the header move to the hamburger menu. This seems like
the answer there waiting for them seems
like it would be helpful. I'm not always a fan of the long scroll
single page approach to this, but it seems like it might make sense
for the narrow screen case. Best!
Tom
On Tue, Sep 1, 2020 at 9:44 AM TEC wrote:
>
>
> Hello everyone :)
>
> The end
required.
* Use the code
:PROPERTIES:
:header-args:python: :prologue "<>"
:END:
#+name: python-helper
#+begin_src python
asdf = lambda : 'result'
#+end_src
#+begin_src python :noweb yes
return asdf()
#+end_src
On Fri, Aug 7, 2020 at 9:20 PM Tom Gillespie wrote:
>
> H
Hah, this is what I get for not reading carefully enough. I wonder if
it is possible to stick <> in the prologue and have it
expand.
On Fri, Aug 7, 2020 at 9:18 PM Tom Gillespie wrote:
>
> I don't see a direct answer to the original question in the thread, so
> here is an exam
is below. Recall that I use
https://github.com/wallyqs/ob-racket. I use this pattern all over the
place in my org blocks. Best,
Tom
* Use the code
:cache yes"
#+begin_src racket :lang racket/base :noweb yes
<>
(helper-function "this should work")
#+end_src
#+RESULTS:
: this sh
be to get the expanded version of the body passed to
org-confirm-babel-evaluate asap with as few disturbances to the rest
of the code base as possible. Best!
Tom
On Tue, Jul 21, 2020 at 9:20 PM Kyle Meyer wrote:
>
> Tom Gillespie writes:
>
> > On Sun, Jul 19, 2020 at 2:13 PM Ky
Hi Kyle,
Thank you for the feedback. In short if modifying (nth 1 info) in place won't
cause a problem then I think it is the way to go. Details below. Best,
Tom
On Sun, Jul 19, 2020 at 2:13 PM Kyle Meyer wrote:
>
> Tom Gillespie writes:
>
> > This is a patch to impro
n up a remote racket session or connect to
one and then run the block in that session. Don't let this stop you though :)
Best!
Tom
!
Tom
From 6d069f9532f44ee9fbc1a0ebdaadcc2eb807f8ec Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Mon, 13 Jul 2020 12:04:18 -0700
Subject: [PATCH] lisp/ob-core.el: pass expanded body to
org-confirm-babel-evaluate
* lisp/ob-core.el (org-babel-get-body-to-eval): New function extracted
from org
L)"])
("help" :follow org-link--open-help)
("file" :complete org-link-complete-file)
("elisp" :follow org-link--open-elisp) ("doi" :follow
org-link--open-doi))
org-latex-format-headline-function 'org-latex-format-headline-default-function
org-link-elisp-confirm-function 'yes-or-no-p
org-latex-format-inlinetask-function
'org-latex-format-inlinetask-default-function
org-html-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
org-html-format-headline-function 'org-html-format-headline-default-function
)
--
Tom Alexander
-Blocks.html. Best,
Tom
On Mon, Mar 2, 2020 at 1:34 PM André Alexandre Gomes
wrote:
>
>
> 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/Feed
are the stdout. This is also true for sh and shell language
options. Maybe that was a recent change, but I just tested with emacs
-q and (org-version) -> 9.1.9 and am getting stdout (as seen below). I
have included the results of org-submit-bug-report for reference.
Best,
Tom
#+begin_src bash
a shell function, then pipe would be the more appropriate default
behavior than `$?`. I think that the underlying principle can be
applied to other languages as well to arrive at sane defaults.
Thoughts?
Tom
On Sat, Feb 29, 2020 at 7:41 AM Jack Kamm wrote:
>
> Sorry, I was confused
, but I guess that can wait. Thus, definitely ok to ignore
this patch. Best!
Tom
On Sun, Feb 16, 2020 at 8:16 PM Kyle Meyer wrote:
>
> Hi Tom,
>
> Tom Gillespie writes:
>
> > Hi all,
> > After hours of frustration ending in a realization that I should really
>
work is needed. Thanks!
Tom
From 362a45ff172af3f49050964aa8534d11374934ca Mon Sep 17 00:00:00 2001
From: Tom Gillespie
Date: Sun, 16 Feb 2020 19:21:16 -0800
Subject: [PATCH] org-src: Add option to restore window configuration after
edit
* lisp/org-src.el: Add an option to restore the previous
Great thanks!
On Thu, Jan 9, 2020 at 8:50 AM Nicolas Goaziou wrote:
> I removed this since you have signed FSF papers.
Got it, I'll leave it out in the future and add a note in
org-contribute.org in case someone
else missed the implication of that paragraph.
Hi,
This is a tiny change to the manual to account for the change from org
-> ol in the org-man example. There may be other references in the
manual that have similar issues but I did not check.
Tom
From b2b8088f958379552f5c9dc228dcda56b7e6f738 Mon Sep 17 00:00:00 2001
From: Tom Gillespie
D
because since they would entail quite a bit of
additional work that is out of scope for this patch. The rx changes
mean that the patch is now over the tiny change limit, I went ahead
and sent a request to ass...@gnu.org so we don't have to wait around
if things look good. Best,
Tom
From
Adam Porter writes:
> May I recommend using the rx macro for regexps? They are much easier
> for humans to parse, which helps reduce errors like the ones mentioned
> here. And they are about to gain some very useful new features
> in Emacs 27.
Yep. I'll switch the regex in over to use rx.
Thank you very much for the feedback. I will make the additional fixes
against maint along with the changes for clarity and send them along
tomorrow. Additional replies in line. Best,
Tom
On Thu, Dec 12, 2019 at 12:40 AM Nicolas Goaziou wrote:
>
> Hello,
>
> Tom Gille
This patch is a change to how org fontifies verbatim source blocks re: [1].
Hopefully it answers Nicolas's question from that thread. Best!
Tom
On Sun, Dec 8, 2019 at 12:05 AM Nicolas Goaziou wrote:
> I do not understand. Source and example blocks are verbatim blocks,
> whereas verse
Hi Nicolas,
Thanks for the reply and pointer to the docs. Given that the
headlines are working as expected, is there the possibility to
change how the syntax highlighting for source and example
blocks works so that it matches the behavior for the verse blocks?
Best,
Tom
On Sat, Dec 7, 2019
-gnu, X toolkit)
of 2019-09-27
Package: Org mode version 9.3 (9.3-elpaplus @
/home/tom/.emacs.d/elpa/org-plus-contrib-20191203/)
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/usr/share/emacs/26.3/lisp/org/)
org-bug-1.org
Description: Lotus Organizer
-linux-gnu, X toolkit)
of 2019-09-27
Package: Org mode version 9.3 (9.3-elpaplus @
/home/tom/.emacs.d/elpa/org-plus-contrib-20191203/)
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/usr/share/emacs/26.3/lisp/org/)
org-bug-0-0.org
Description: Lotus Organizer
org-bug-0-1.org
rote:
On Sat, Oct 13, 2018 at 1:56 AM Colin Baxter wrote:
Tom Burbage writes:
> When I use simple lists, I would like to be able to mix in '!' and
> '?' with '-' as these are sometimes more expressive of what the
> list item represents. My request is that the list of char
When I use simple lists, I would like to be able to mix in '!' and '?'
with '-' as these are sometimes more expressive of what the list item
represents.
My request is that the list of characters org-list recognizes as being a
valid "bullet" be customizable by the user.
On Thu, Aug 2, 2018 at 8:13 AM tom wrote:
> You guys are so skillful and awesome you helped me without saying a word!
>
> After looking around at
>
> https://emacs.stackexchange.com/questions/477/how-do-i-automatically-save-org-mode-buffers
>
> I just added a third hook,
>
this solved. Org rocks, I don't rock.
On Wed, Aug 1, 2018 at 8:41 AM tom wrote:
> Me again. Let me try to provide a bit more info. I'm using xdotool to call
> "emacsclient -c -e '(org-capture)'". In my init.el, I have both
>
> (add-hook 'org-capture-mode-hook 'make-frame)
> and
ase, may I have some help with the modification? Or am I missing something
else?
Thanks.
On Fri, Jul 27, 2018 at 7:42 PM tom wrote:
> Hey guys, I have a capture template set up pretty much the way I want it,
> but the file it writes to does not save afterwards. It's a table line
> templat
201 - 300 of 525 matches
Mail list logo
