Re: [PATCH] org-manual.org: Augment TODO keywords example
Marking as cancelled for updates.orgmode.org
Re: [PATCH] org-manual.org: Augment TODO keywords example
Marking as cancelled for updates.orgmode.org
Re: Switching to new Git repositories
On 23 September 2021, No Wayman wrote: There is a bug in mk/targets.mk introduced by 61336f80dc. As others have pointed out, the new repository does not have tags. As a fallback, org.el's version is read in it's header. However, it looks like Kyle forgot to trim that string so we get ORGVERSION set to "9.5-dev" instead of "9.5". This causes `org-version' to return an incorrect version string. This is an interesting bug---a tiny thing that never mattered until it turned into problem when triggered by a minor part of the process of moving Git repos from one place to another. My sincere thanks to everyone who looked into it, and found causes and fixes. Such is Org development: on the one hand, years of intricate work to build a powerful citation system, on the other, removing "-dev" from a string. Bill -- William Denton https://www.miskatonic.org/ Librarian, artist and licensed private investigator. Toronto, Canada
Re: Exporting: how to exclude top/bottom hline for tables?
Hi, On Thu, Sep 23, 2021 at 5:09 AM S Boucher wrote: > > Is there a way to exclude the top and bottom hline of tables during export? I don't see any option to change. But you can do: , | (defun my/remove-bottom (borders) | (remove-if (lambda (x) (memq x '(bottom top above below))) borders)) | (advice-add 'org-export-table-cell-borders :filter-return #'my/remove-hlines) ` tweak the list to change the behaviour. > When I'm exporting to UTF-8, the top and bottom lines of the tables do not > display correctly for me. > > Though the number of chars is correct, the face used by emacs does not match > the face used for the rest of the file. I guess fixing the faces is the right way forward. -- yashi
Re: Switching to new Git repositories
No Wayman writes: > Out of curiosity I ran this against the repo to see if the > "Version" metadata had always followed its current convention: > > git grep "Version:" $(git rev-list --all) -- lisp/org.el > > Looks like the "-dev" suffix goes back to "9.4-dev" and before > that we have "8.4-git" and "6.08-pre01". > I'm not sure what Org's convention is here, but the patsubst could > be adjusted to be more flexible if necessary. Thanks for checking. I think just handling -dev is probably good enough. > Subject: [PATCH] mk/targets.mk: Fix ORGVERSION in tag-less repos Pushed: To git.savannah.gnu.org:/srv/git/emacs/org-mode.git c9dc6603a..9a4a24a94 main -> main (It's not needed on the bugfix branch given -dev isn't used in the header there. Plus I think the 9.5 release is expected before another release from maint/bugfix.) Thank you for fixing my mistake.
[PATCH] org-manual.org: Augment TODO keywords example
Aloha all, The attached patch makes the example for setting up keywords in an individual file match the example where it appears earlier. It also provides an example of how fast TODO selection should look when it is implemented on a per-file basis. Sorry for the earlier truncated messages! Clumsy fingers today! All the best, Tom >From 47b9eb04e55530ecc7b13411c01cd6fb97b17d14 Mon Sep 17 00:00:00 2001 From: "Thomas S. Dye" Date: Thu, 23 Sep 2021 13:55:19 -1000 Subject: [PATCH] org-manual.org: Augment TODO keywords example --- doc/org-manual.org | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index 87f2147f2..c27a2c07c 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -3991,9 +3991,9 @@ interpretation, but it means the same as =#+TODO=, or A setup for using several sets in parallel would be: #+begin_example -,#+TODO: TODO | DONE -,#+TODO: REPORT BUG KNOWNCAUSE | FIXED -,#+TODO: | CANCELED +,#+TODO: TODO(t) | DONE(d) +,#+TODO: REPORT(r) BUG(b) KNOWNCAUSE(k) | FIXED(f) +,#+TODO: | CANCELED(c) #+end_example #+cindex: completion, of option keywords -- 2.25.1 -- Thomas S. Dye https://tsdye.online/tsdye
[PATCH] org-manual.org: Augment TODO keywords example
Aloha all, The attached patch -- Thomas S. Dye https://tsdye.online/tsdye
[PATCH] org-manual.org: Augment TODO keywords example
Aloha all, The attached patch makes the example for setting up keywords in an individual file match the example where it appears earlier. It also provides an example of how fast TODO selection should look when it is implemented on a per-file basis. Sorry for the earlier truncated message. All the best, Tom -- Thomas S. Dye https://tsdye.online/tsdye
Re: toggle-truncate-lines outside table and source regions
almost as if truncate line feature should be a text property? good idea to take up with devs if no solution arrives. source blocks have c-c '; idk about tables. perhaps you could at least have ugliness in the outline but correctness in editing. On 9/23/21, Bill Burdick wrote: > Gah, sorry about that -- I didn't read your message carefully enough! > > > -- Bill > > > On Thu, Sep 23, 2021 at 4:56 AM Luca Ferrari wrote: > >> On Wed, Sep 22, 2021 at 3:49 PM Bill Burdick >> wrote: >> > >> > How about adding >> > >> > (lambda () (toggle-truncate-lines 1)) >> > >> > to org-mode-hooks in your EMACS init file? >> >> isn't this the same as M-x toggle-truncate-lines ? Because it will >> truncate every line, but I'm searching for a way to truncate only >> text, and not tables nor code. >> AM I misunderstanding your suggestion? >> >> Luca >> > -- The Kafka Pandemic Please learn what misopathy is. https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
Re: Switching to new Git repositories
On 09/23/21 17:17:48 -0400, No Wayman wrote: >> Sounds like a weird issue. I don't think this 9.5-dev tag is >> something from the Org repo. > > There is a bug in mk/targets.mk introduced by 61336f80dc. Quoting that commit message for context: mk/targets.mk: Add version fallback for tag-less repos * mk/targets.mk (ORGVERSION, GITVERSION): Get version from lisp/org.el header if it can't be retrieved from git-describe. As of elpa.git's ee03829f90 (Finalize the new master branch, 2020-12-14), org-release and org-git-version are empty strings in https://elpa.gnu.org/packages/org-*.tar files. This is because the new setup executes `make autoloads info' in an elpa.git worktree with an Org branch checked out, but elpa.git of course doesn't have Org's release tags. Maintaining the org.el version header has been a point of contention in the past [1], but the header has been there for a while now. Use it to avoid the above elpa.git issue. In the case of the master branch, the org-release value generated in a tag-less repo will have a different version than the one from a regular repo because org.el's version header has a "-dev" suffix, but that's still better than an empty version. [...] > As others have pointed out, the new repository does not have tags. > As a fallback, org.el's version is read in it's header. > However, it looks like Kyle forgot to trim that string so we get > ORGVERSION set to "9.5-dev" instead of "9.5". I of course can't say for sure, but based on my commit message (in particular the last paragraph), it sounds like I was aware of the discrepancy but didn't realize it'd cause the downstream "Invalid version syntax" issue mentioned by Bill in . > This causes `org-version' to return an incorrect version string. > > The attached patch addresses the issue in the makefile. Thanks. > Subject: [PATCH] mk/targets.mk: Fix ORGVERSION in tag-less repos > > * mk/targets.mk (ORGVERSION, GITVERSION): properly generate ORGVERSION. I think it'd be better to say something more specific about the change rather than say "properly" and assume the reader knows what the writer has in mind. > Fix bug introduced 61336f80 which caused ORGVERSION to be generated as > "Major.Minor-dev" instead of "Major.Minor" in tag-less repos. Please say what the bug is. Can you give a sparse outline of the call chain for the error mentioned in Bill's message? > -ORGVERSION := $(shell $(BATCH) --eval "(require 'lisp-mnt)" \ > - --visit lisp/org.el --eval '(princ (lm-header "version"))') > -GITVERSION ?= $(ORGVERSION)-g$(shell git rev-parse --short=6 HEAD) > +ORGVERSION := $(patsubst %-dev,%,$(shell $(BATCH) --eval "(require > 'lisp-mnt)" \ > + --visit lisp/org.el --eval '(princ (lm-header "version"))')) > +GITVERSION ?= $(ORGVERSION)-g$(shell git rev-parse --short=6 HEAD)) It looks like you've unintentionally added a ')' to the end of the GITVERSION line. Another approach would be to update org.el's version to contain something that still signals "-dev" but won't trigger the "Invalid version syntax" (which, based on grepping the Emacs repo, is signaled by version-to-list). But given that in the current setup a clone with tags wouldn't use the header version, stripping -dev for consistency sounds like the way to go.
Re: Switching to new Git repositories
Sounds like a weird issue. I don't think this 9.5-dev tag is something from the Org repo. There is a bug in mk/targets.mk introduced by 61336f80dc. As others have pointed out, the new repository does not have tags. As a fallback, org.el's version is read in it's header. However, it looks like Kyle forgot to trim that string so we get ORGVERSION set to "9.5-dev" instead of "9.5". This causes `org-version' to return an incorrect version string. The attached patch addresses the issue in the makefile. >From 9b81f396e69af146faceb13f5602fb6aa06a84e0 Mon Sep 17 00:00:00 2001 From: Nicholas Vollmer Date: Thu, 23 Sep 2021 17:13:34 -0400 Subject: [PATCH] mk/targets.mk: Fix ORGVERSION in tag-less repos * mk/targets.mk (ORGVERSION, GITVERSION): properly generate ORGVERSION. Fix bug introduced 61336f80 which caused ORGVERSION to be generated as "Major.Minor-dev" instead of "Major.Minor" in tag-less repos. --- mk/targets.mk | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/mk/targets.mk b/mk/targets.mk index 693e3781f..35383f173 100644 --- a/mk/targets.mk +++ b/mk/targets.mk @@ -15,9 +15,9 @@ ifneq ($(wildcard .git),) ifeq ($(ORGVERSION),) # In elpa.git, there are no tags available. Fall back to using # the org.el header. -ORGVERSION := $(shell $(BATCH) --eval "(require 'lisp-mnt)" \ - --visit lisp/org.el --eval '(princ (lm-header "version"))') -GITVERSION ?= $(ORGVERSION)-g$(shell git rev-parse --short=6 HEAD) +ORGVERSION := $(patsubst %-dev,%,$(shell $(BATCH) --eval "(require 'lisp-mnt)" \ + --visit lisp/org.el --eval '(princ (lm-header "version"))')) +GITVERSION ?= $(ORGVERSION)-g$(shell git rev-parse --short=6 HEAD)) else GITVERSION ?= $(shell git describe --match release\* --abbrev=6 HEAD) endif -- 2.33.0
Re: Switching to new Git repositories
William Denton writes: > I'm seeing exactly the same, and the suggested rebase commands didn't change > it. > > I wonder if it's related to a problem I have on one of the two > machines (both Ubuntu, with identical setups) where I run Org from > source. > > On one, when I switched to the new repo, I got this on startup: > > Error (use-package): org/:catch: Invalid version syntax: ‘9.5-dev’ > > I can't see what causes that. I use use-package to set up Org in my > init file¹ but it seems to be some internal problem, because I don't > mention anything about versions. > > What's more, on my other machine, where everything about Emacs is > identical, it works without any problem (even though there are no > tags). Sounds like a weird issue. I don't think this 9.5-dev tag is something from the Org repo. Have you already tried to turn it off and on again? I.e. delete your local repo and start with a fresh clone? Of course take care not to loose any data important to you! HTH
Re: Switching to new Git repositories
> Éibhear writes: > On 23/09/2021 19:06, William Denton wrote: >> I'm seeing exactly the same, and the suggested rebase commands >> didn't change it. > I'm guessing it's just that in the migration from code.orgmode.org > to git.savannah.gnu.org, the step to push the tags was not > performed: > =8<- > $ git push --tags > https://git.savannah.gnu.org/git/emacs/org-mode.git > =8<- > Even though the branch names are different, the commit SHAs are > the same for both remotes, to this command would do it. > I just wonder if it's because there's something else planned for > the tags, or if this was just an oversight. > Éibhear Good point. I'll wait a few days to see what happens before following Marco's suggestion of bringing over the tags manually. -- Cut --- Best wishes, Colin Baxter. signature.asc Description: PGP signature
Re: Switching to new Git repositories
Hi! Colin Baxter writes: >> Nick Dokos writes: > > > FWIW, I get $ git remote -v upstream > > https://git.savannah.gnu.org/git/emacs/org-mode.git (fetch) > > upstream https://git.savannah.gnu.org/git/emacs/org-mode.git > > (push) > > > $ git tag | wc -l 386 > > > Maybe do > > > $ git remote update $ git rebase > > > and try again? > > Doesn't work for me. I did all above but still get zero for git tag | wc What about adding the still existing Org repo temporarily and fetching the tags from there? Example: cd PATHTOORGMODE git remote -v git remote add olderrepo https://code.orgmode.org/bzg/org-mode.git git remote -v git fetch olderrepo 'refs/tags/*:refs/tags/*' git remote remove olderrepo git remote -v Enjoy the tags in your local repo! I guess the maintainers will push the right tags to the new repo soon.
Re: Switching to new Git repositories
On 23/09/2021 19:06, William Denton wrote: > I'm seeing exactly the same, and the suggested rebase commands didn't > change it. I'm guessing it's just that in the migration from code.orgmode.org to git.savannah.gnu.org, the step to push the tags was not performed: =8<- $ git push --tags https://git.savannah.gnu.org/git/emacs/org-mode.git =8<- Even though the branch names are different, the commit SHAs are the same for both remotes, to this command would do it. I just wonder if it's because there's something else planned for the tags, or if this was just an oversight. Éibhear > > I wonder if it's related to a problem I have on one of the two machines > (both Ubuntu, with identical setups) where I run Org from source. > > On one, when I switched to the new repo, I got this on startup: > > Error (use-package): org/:catch: Invalid version syntax: ‘9.5-dev’ > > I can't see what causes that. I use use-package to set up Org in my > init file¹ but it seems to be some internal problem, because I don't > mention anything about versions. > > What's more, on my other machine, where everything about Emacs is > identical, it works without any problem (even though there are no tags). > > Bill > > > ¹ https://github.com/wdenton/.emacs.d/blob/master/init.org > > > On 23 September 2021, Éibhear wrote: > >> On 20/09/2021 05:37, Bastien wrote: >>> Hi all, >>> >>> from now on, here are the official Org repositories: >>> >>> - org-mode: https://git.savannah.gnu.org/cgit/emacs/org-mode.git >>> - worg: https://git.sr.ht/~bzg/worg >>> - orgweb: https://git.sr.ht/~bzg/orgweb >> >> Hi, >> >> We're the tags missed in the migration across to savannah? >> >> Thanks, >> >> Éibhear >> >> =8<- >> >> $ git -C org-mode.orig remote -v >> origin https://code.orgmode.org/bzg/org-mode.git (fetch) >> origin https://code.orgmode.org/bzg/org-mode.git (push) >> >> $ git -C org-mode.orig tag | wc -l >> 385 >> >> $ git -C org-mode.orig tag | tail -5 >> release_9.4.2 >> release_9.4.3 >> release_9.4.4 >> release_9.4.5 >> release_9.4.6 >> >> $ git -C org-mode.new remote -v >> origin https://git.savannah.gnu.org/git/emacs/org-mode.git (fetch) >> origin https://git.savannah.gnu.org/git/emacs/org-mode.git (push) >> >> $ git -C org-mode.new tag | wc -l >> 0 >> >> =8<- >> >>> >>> org-contrib will continue to be on https://git.sr.ht/~bzg/org-contrib >>> until it disappears, thanks to volunteers taking over maintainance of >>> the various packages. >>> >>> You can forget code.orgmode.org. >>> >>> If you commit to code.orgmode.org by mistake instead of using the new >>> repos, just merge the commit from the old repo that you can set up as >>> a remote branch: I won't delete code.orgmode.org until Org 9.6. >>> >>> If you don't have write access to the new repos and think you should, >>> please send me an email. >>> >>> I will work on merging orgweb+worg and setting up the HTML publication >>> process from sr.ht, which can take a while. >>> >>> Have a nice week! >>> >> >> >> > > -- > William Denton > https://www.miskatonic.org/ > Librarian, artist and licensed private investigator. > Toronto, Canada -- Éibhear Ó hAnluain Dublin, Ireland. +---+-+ | e-mail: eibhear@gmail.com | Web: [http://www.gibiris.org/] | | Mobile: +353 86 856 5666 | Matrix: @eibhear:matrix.gibiris.org | | Twitter: @eibhear | | +---=-+ | If you would like help getting started using the Element and Matrix | | messaging system, at home or in work, please let me know. | +-+ OpenPGP_signature Description: OpenPGP digital signature
Re: Switching to new Git repositories
I'm seeing exactly the same, and the suggested rebase commands didn't change it. I wonder if it's related to a problem I have on one of the two machines (both Ubuntu, with identical setups) where I run Org from source. On one, when I switched to the new repo, I got this on startup: Error (use-package): org/:catch: Invalid version syntax: ‘9.5-dev’ I can't see what causes that. I use use-package to set up Org in my init file¹ but it seems to be some internal problem, because I don't mention anything about versions. What's more, on my other machine, where everything about Emacs is identical, it works without any problem (even though there are no tags). Bill ¹ https://github.com/wdenton/.emacs.d/blob/master/init.org On 23 September 2021, Éibhear wrote: On 20/09/2021 05:37, Bastien wrote: Hi all, from now on, here are the official Org repositories: - org-mode: https://git.savannah.gnu.org/cgit/emacs/org-mode.git - worg: https://git.sr.ht/~bzg/worg - orgweb: https://git.sr.ht/~bzg/orgweb Hi, We're the tags missed in the migration across to savannah? Thanks, Éibhear =8<- $ git -C org-mode.orig remote -v origin https://code.orgmode.org/bzg/org-mode.git (fetch) origin https://code.orgmode.org/bzg/org-mode.git (push) $ git -C org-mode.orig tag | wc -l 385 $ git -C org-mode.orig tag | tail -5 release_9.4.2 release_9.4.3 release_9.4.4 release_9.4.5 release_9.4.6 $ git -C org-mode.new remote -v origin https://git.savannah.gnu.org/git/emacs/org-mode.git (fetch) origin https://git.savannah.gnu.org/git/emacs/org-mode.git (push) $ git -C org-mode.new tag | wc -l 0 =8<- org-contrib will continue to be on https://git.sr.ht/~bzg/org-contrib until it disappears, thanks to volunteers taking over maintainance of the various packages. You can forget code.orgmode.org. If you commit to code.orgmode.org by mistake instead of using the new repos, just merge the commit from the old repo that you can set up as a remote branch: I won't delete code.orgmode.org until Org 9.6. If you don't have write access to the new repos and think you should, please send me an email. I will work on merging orgweb+worg and setting up the HTML publication process from sr.ht, which can take a while. Have a nice week! -- William Denton https://www.miskatonic.org/ Librarian, artist and licensed private investigator. Toronto, Canada
Re: Switching to new Git repositories
> Nick Dokos writes: > FWIW, I get $ git remote -v upstream > https://git.savannah.gnu.org/git/emacs/org-mode.git (fetch) > upstream https://git.savannah.gnu.org/git/emacs/org-mode.git > (push) > $ git tag | wc -l 386 > Maybe do > $ git remote update $ git rebase > and try again? Doesn't work for me. I did all above but still get zero for git tag | wc Best wishes,
Re: [PATCH] ox.el: add smart quotes for Greek
Hi Maxim, Max Nikulin writes: > Juan Manuel, I feel some misunderstanding. I am not asking for more > arguments in support of current variant of patch. CLDR entry, EU > recommendations, the mail from Protesilaos, absence of named HTML > entity, complications with pdfTeX are more than enough. I completely agree with what you say, but I think I have explained wrong in my previous mail. I said about consulting YH because his article is something old (90s), and his current opinion on "the state of the question" could help me compose my little explanatory note. And in any case, I think everyone here agrees that the character that he proposed in his paper is unfeasible in Org, for all the reasons you have summarized. On the other hand, the orthographic norms are not sacred norms; rather, they are determined by use and customs. For example, here in Spain the manuals and treatises tend to disagree on certain issues. In my opinion, many times it is better to talk about trends more than norms[1], and trends that more or less end imposing, almost by mere natural selection (another matter is that sometimes bad habits are also imposed, for using inappropriate software, but this is not the case where we are). [1] For example, in Spanish of Spain, the quotation marks are «“ ”», But in Mexican Spanish they use “‘’” as in English. In fact the csquotes LaTeX package includes both styles. Best regards, Juan Manuel
Re: org-cite not mentioned in ORG-NEWS for 9.5
Pretty sure it just means no documentation has yet been written for it. On Thu, Sep 23, 2021 at 10:19 AM Kai von Fintel wrote: > > In a recent message there was a pointer to the etc/ORG-NEWS file located at > > http://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/etc/ORG-NEWS > > I take it that this includes the release notes in progress for the upcoming > 9.5 release. > > There is no mention of the new org-cite functionality in that file. Does this > mean that org-cite will not be part of the 9.5 release? > > -- Kai. >
Re : Re: Capture abort: Symbol’s function definition is void: turn-on-org-provide
Le jeudi 23 septembre 2021 à 18:12, Ihor Radchenko a écrit
:
> Joseph Vidal-Rosset jos...@vidal-rosset.net writes:
>
> > But nowhere in this file have function " turn-on-org-provide" . :(
> >
> > A suggestion?
>
> Try to setting debug-on-error to 't and share backtrace of the error.
>
> Best,
>
> Ihor
I got the following backtrace:
#[512 \203\0 \306=\203\0\307\310\232!\311\267\202 \0\312!\207\313
\207p\314\303!\203/\0 \203/\0\315 \316"\202<\0\3171:\0\320\321!0\202<\0\210\321
\206C\0\322!\321@\206R\0\323 \205R\0`\324
{\262\211;\203a\0\325\326G\327$\210;\203o\0\325\326G\330$\210\331\267\202\201\0\332\333!\202\204\334\335!\202\204\336!\210\337
\210\340\341\342\343!\206\240\0\344\345!\205\240\0\346A"@\347\343
!\205\256\0\350\343 !!\316
\351
\352\353 \354
\206\276\0\355 &\210\356\326\232\205\312\0\357!\210\3601\331\0\340\361\362
"0\202\353\0\363\364!\203\343\0\365\364!\210\366\367\370!"\262\210\371\372!B\3731\374\371\375!@\376=!0\2020\377p!\203\201E\0\201F\0\201G\0
"\203\365p!\210\201H\0\371\352!!\210\366\201I\0\371\201J\0!\370!#\262\210\201K\0\201L\0!\203x\371\201M\0!\203x\201N\01s\201O\0
\203\\340\201P\0\201Q\0C!"\210\201R\0
\210\201S\0\201D\0!\210\201T\0\211D0\202w\210\202x\210\371\201U\0!\205\204\201V\0
\207 [org-capture-use-agenda-date major-mode org-overriding-default-time
org-capture-link-is-already-stored org-store-link-plist org-capture-entry
org-agenda-mode org-get-cursor-date 1 #s(hash-table size 2 test equal
rehash-size 1.5 rehash-threshold 0.8125 purecopy t data ((4) 22 (16) 26)) ...]
21 (/home/joseph/.emacs.d/elpa/org-plus-contrib-20210920/org-capture.elc .
24239) P]: Capture abort: Symbol’s function definition is void:
turn-on-org-provide
If this backtrace provides some clue... please, telle me.
All the best,
Jo.
Re: Capture abort: Symbol’s function definition is void: turn-on-org-provide
Joseph Vidal-Rosset writes: > But nowhere in this file have function " turn-on-org-provide" . :( > > A suggestion? Try to setting debug-on-error to 't and share backtrace of the error. Best, Ihor
Re: Capture abort: Symbol’s function definition is void: turn-on-org-provide
you should use describe-variable on org-capture-templates. Maybe some other
package has added to it.
John
---
Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Thu, Sep 23, 2021 at 12:01 PM Joseph Vidal-Rosset <
jos...@vidal-rosset.net> wrote:
>
>
> Le 23/09/2021 à 17:28, Daniel Fleischer a écrit :
> > Joseph Vidal-Rosset writes:
> >
> >> To capture an email and to link this message for gnus, I get now this
> >> error message:
> >>
> >> Capture abort: Symbol’s function definition is void: turn-on-org-provide
> >
> > What is your capture template?
> >
> > --
> >
> > Daniel Fleischer
>
> In myagenda.el I have this function:
>
> (setq org-capture-templates
>'(
> ("t" "todo" entry (file+headline "~/Dropbox/Orgzly/todo.org"
> "Tasks")
> "* TODO [#A] %?\n
> [[~/Dropbox/Orgzly/links.org::%(org-insert-time-stamp (org-read-date nil
> t \"%:date\"))]] \n* %(org-insert-time-stamp (org-read-date nil t
> \"%:date\")) %a "
> )
> ("n" ; key
> "note" ;name
> entry;type
> (file+headline "~/Dropbox/Orgzly/notes.org" "Notes") ;target
> "* NOTE du %(org-insert-time-stamp (org-read-date nil t
> \"%:date\")) \n Voir %a " ; template
> )
> ("H" "HOWTO: C-c C-s : schedule ; C-c C-d : deadline ; C-c C-w :
> org-refile at a point; last: C-c C-t : DONE - F11-a: org-archive"
> entry (file+headline "" "") ""
> )
> )
>)
>
> But nowhere in this file have function " turn-on-org-provide" . :(
>
> A suggestion?
>
> Many thanks,
>
> Jo.
>
>
>
Re: [PATCH] ox.el: add smart quotes for Greek
On 23/09/2021 02:55, Juan Manuel Macías wrote: Before uploading a corrected version of the patch (with a small explanatory note), I could consult Haralambous himself by mail, and ask him what he thinks of this question... Juan Manuel, I feel some misunderstanding. I am not asking for more arguments in support of current variant of patch. CLDR entry, EU recommendations, the mail from Protesilaos, absence of named HTML entity, complications with pdfTeX are more than enough. Some degree of uncertainty during software development is unavoidable, so it is perfectly OK to proceed with the variant you have proposed. It is better to address other issues. I suggest just to document the decision, to mention pros and cons. There is a little chance that the decision might be reconsidered later and it is not a problem. It would be nice to provide useful hints for participants of future discussion. Even information that another language was added not just for completeness and with guessed values might be helpful.
Re: Capture abort: Symbol’s function definition is void: turn-on-org-provide
Le 23/09/2021 à 18:02, John Kitchin a écrit : > you should use describe-variable on org-capture-templates. Maybe some > other package has added to it. > John Many thanks John, I am going to try this way! Best wishes, Jo.
Re: Capture abort: Symbol’s function definition is void: turn-on-org-provide
Le 23/09/2021 à 17:28, Daniel Fleischer a écrit :
> Joseph Vidal-Rosset writes:
>
>> To capture an email and to link this message for gnus, I get now this
>> error message:
>>
>> Capture abort: Symbol’s function definition is void: turn-on-org-provide
>
> What is your capture template?
>
> --
>
> Daniel Fleischer
In myagenda.el I have this function:
(setq org-capture-templates
'(
("t" "todo" entry (file+headline "~/Dropbox/Orgzly/todo.org" "Tasks")
"* TODO [#A] %?\n
[[~/Dropbox/Orgzly/links.org::%(org-insert-time-stamp (org-read-date nil
t \"%:date\"))]] \n* %(org-insert-time-stamp (org-read-date nil t
\"%:date\")) %a "
)
("n" ; key
"note" ;name
entry;type
(file+headline "~/Dropbox/Orgzly/notes.org" "Notes") ;target
"* NOTE du %(org-insert-time-stamp (org-read-date nil t
\"%:date\")) \n Voir %a " ; template
)
("H" "HOWTO: C-c C-s : schedule ; C-c C-d : deadline ; C-c C-w :
org-refile at a point; last: C-c C-t : DONE - F11-a: org-archive"
entry (file+headline "" "") ""
)
)
)
But nowhere in this file have function " turn-on-org-provide" . :(
A suggestion?
Many thanks,
Jo.
org-roam on termux?
Dear list, has anybody managed to get org-roam working on Emacs on termux on Android? I am having problems getting the SQL backend that org-roam uses working. I'm not up to speed with termux so any suggestions welcome! Thank you, eric -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-660-gf33b92 : Latest paper written in org: https://arxiv.org/abs/2106.05096
Re: Capture abort: Symbol’s function definition is void: turn-on-org-provide
Joseph Vidal-Rosset writes: > To capture an email and to link this message for gnus, I get now this > error message: > > Capture abort: Symbol’s function definition is void: turn-on-org-provide What is your capture template? -- Daniel Fleischer
Re: Switching to new Git repositories
FWIW, I get $ git remote -v upstreamhttps://git.savannah.gnu.org/git/emacs/org-mode.git (fetch) upstreamhttps://git.savannah.gnu.org/git/emacs/org-mode.git (push) $ git tag | wc -l 386 Maybe do $ git remote update $ git rebase and try again? -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler
Re: [PATCH] Fix some typos
On 23/09/2021 03:18, Juan Manuel Macías wrote: Max Nikulin writes: However there is namely "memory" in the "1609 Quarto", see e.g. https://en.wikipedia.org/wiki/Sonnet_1 Web pages with the same variant as in the Org manual do not mention the source (particular edition). I hope, I just do not know what is considered as the canonical variant for not so old language. I am not an expert on Shakespeare's poetry either, but as the author of the patch where Sonnet 1 is included, I can say that 'memeory' is a typo (sorry). At least I didn't use that word intentionally. I don't know if there is any textual variant 'memeory', but in my case it is nothing more than a simple typo :-). Then "mught" should be another typo. "His tender heire might beare his memory:" - 1609 Quatro "His tender heir might bear his memory:" - Wikipedia citing Shakespeare, William. Duncan-Jones, Katherine. Shakespeare’s Sonnets. Bloomsbury Arden 2010. p. 113 ISBN 9781408017975 "His tender heir mught bear his memeory:" - some web pages and Org manual.
org-cite not mentioned in ORG-NEWS for 9.5
In a recent message there was a pointer to the etc/ORG-NEWS file located at http://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/etc/ORG-NEWS I take it that this includes the release notes in progress for the upcoming 9.5 release. There is no mention of the new org-cite functionality in that file. Does this mean that org-cite will not be part of the 9.5 release? -- Kai.
Re: toggle-truncate-lines outside table and source regions
Gah, sorry about that -- I didn't read your message carefully enough! -- Bill On Thu, Sep 23, 2021 at 4:56 AM Luca Ferrari wrote: > On Wed, Sep 22, 2021 at 3:49 PM Bill Burdick > wrote: > > > > How about adding > > > > (lambda () (toggle-truncate-lines 1)) > > > > to org-mode-hooks in your EMACS init file? > > isn't this the same as M-x toggle-truncate-lines ? Because it will > truncate every line, but I'm searching for a way to truncate only > text, and not tables nor code. > AM I misunderstanding your suggestion? > > Luca >
Re : Capture abort: Symbol’s function definition is void: turn-on-org-provide
I did not say that I'm using Prelude Emacs. Maybe it can be useful to solve my problem. ‐‐‐ Original Message ‐‐‐ Le jeudi 23 septembre 2021 à 14:38, Joseph Vidal-Rosset a écrit : > Hello, > > My problem is already explained in the subject of this email. > > To capture an email and to link this message for gnus, I get now this > > error message: > > Capture abort: Symbol’s function definition is void: turn-on-org-provide > > I've tried to Google this bug, getting no result. Your help is welcome. > > Thanks, > > Best wishes, > > Jo.
Org agenda width is one char-column too short
As seen in the linked image, my agenda width is a single char too short so it
clips the last : of the tags. I always use truncate-lines-mode, so this is a
minor inconvenience but might be something easily fixed for new users? I think
it has always done this for me.
https://i.imgur.com/RFRhLMT.png
Here are my configurations for agenda in Straight; if I'm not mistaken, there
is nothing here that should effect things. Everything else is still at the
default. I only got to thinking about this because agenda does such an
admirable job of fitting to screens (something not easy in many emacs
situations).
--8<---cut here---start->8---
(use-package org-agenda
:straight (:type built-in)
:after org
:custom
(org-agenda-restriction-lock-highlight-subtree nil)
(org-agenda-show-outline-path nil)
(org-agenda-fontify-priorities nil)
(org-agenda-restriction-lock-highlight-subtree nil)
:custom-face
(org-agenda-clocking ((t (:background "gold" :foreground "black"
(org-agenda-dimmed-todo-face ((t (:foreground "dimgray"
(org-agenda-calendar-event ((t (:inherit default
(org-agenda-clocking ((t (:background "gold" :foreground "black"
(org-agenda-current-time ((t (:background "blue2" :foreground "white
smoke" :weight ultra-bold
(org-agenda-dimmed-todo-face ((t (:foreground "dimgray"
(org-agenda-done ((t (:inherit org-done :box (:line-width 2 :color
"#00ff00" :style released-button)
:bind (:map org-agenda-mode-map
("p" . org-agenda-show-clocking-issues)
("P" . tsa/org-appts))
:config
(add-hook 'org-agenda-mode-hook (lambda () (toggle-truncate-lines 1)))
)
--8<---cut here---end--->8---
Capture abort: Symbol’s function definition is void: turn-on-org-provide
Hello, My problem is already explained in the subject of this email. To capture an email and to link this message for gnus, I get now this error message: Capture abort: Symbol’s function definition is void: turn-on-org-provide I've tried to Google this bug, getting no result. Your help is welcome. Thanks, Best wishes, Jo.
[org-cite] org-cite-make-insert-processor behavior
If inserting a new org-cite citation, one can insert multiple references. If editing an existing citation, one can only insert one. In ny processor, for example, the user can select multiple references, but org-cite-insert will only insert the first one. Is there a reason for this? Can we change it? Bruce
Re: [PATCH] Fix some typos
Max Nikulin writes: > Please, forgive my ignorance of Shakespeare's poetry. Ignorance is bliss! (Sophocles) > On 17/09/2021 17:05, Marco Wahl wrote: >>> On 17/09/2021 04:40, Stefan Kangas wrote: Please find attached another clean-up patch that fixes a small number of typos. > > Thou shall not change "memeory" to "memory" tho > I think, a bit more is required to avoid recurring attempts to change > spelling if you would like to see such variant. Static code analyzers > usually have a feature that allows to ignore specific warning at a > particular line, see e.g. > https://flake8.pycqa.org/en/latest/user/violations.html#in-line-ignoring-errors > for Python's flake8. > > Maybe "LocalWords:" could do a similar trick for ispell.el at least for > the whole file. Unsure if it is possible to add an exception for the > quote only. Interesting ideas! > However there is namely "memory" in the "1609 Quarto", see e.g. > https://en.wikipedia.org/wiki/Sonnet_1 Web pages with the same variant > as in the Org manual do not mention the source (particular edition). I > hope, I just do not know what is considered as the canonical variant for > not so old language. Same here. I have no idea. What I found suspicious, was the correction occurring in a quote section. But you are right. Since there is no reference to the source the correction is worthy AFAICS. If I'd be the only committer, I'd leave the "memeory" anyway. But go ahead and change the occurance to "memory" if you like. I won't try to stop you.
Re: Switching to new Git repositories
On 20/09/2021 05:37, Bastien wrote: > Hi all, > > from now on, here are the official Org repositories: > > - org-mode: https://git.savannah.gnu.org/cgit/emacs/org-mode.git > - worg: https://git.sr.ht/~bzg/worg > - orgweb: https://git.sr.ht/~bzg/orgweb Hi, We're the tags missed in the migration across to savannah? Thanks, Éibhear =8<- $ git -C org-mode.orig remote -v origin https://code.orgmode.org/bzg/org-mode.git (fetch) origin https://code.orgmode.org/bzg/org-mode.git (push) $ git -C org-mode.orig tag | wc -l 385 $ git -C org-mode.orig tag | tail -5 release_9.4.2 release_9.4.3 release_9.4.4 release_9.4.5 release_9.4.6 $ git -C org-mode.new remote -v origin https://git.savannah.gnu.org/git/emacs/org-mode.git (fetch) origin https://git.savannah.gnu.org/git/emacs/org-mode.git (push) $ git -C org-mode.new tag | wc -l 0 =8<- > > org-contrib will continue to be on https://git.sr.ht/~bzg/org-contrib > until it disappears, thanks to volunteers taking over maintainance of > the various packages. > > You can forget code.orgmode.org. > > If you commit to code.orgmode.org by mistake instead of using the new > repos, just merge the commit from the old repo that you can set up as > a remote branch: I won't delete code.orgmode.org until Org 9.6. > > If you don't have write access to the new repos and think you should, > please send me an email. > > I will work on merging orgweb+worg and setting up the HTML publication > process from sr.ht, which can take a while. > > Have a nice week! > -- Éibhear Ó hAnluain Dublin, Ireland. +---+-+ | e-mail: eibhear@gmail.com | Web: [http://www.gibiris.org/] | | Mobile: +353 86 856 5666 | Matrix: @eibhear:matrix.gibiris.org | | Twitter: @eibhear | | +---=-+ | If you would like help getting started using the Element and Matrix | | messaging system, at home or in work, please let me know. | +-+ OpenPGP_signature Description: OpenPGP digital signature
Re: toggle-truncate-lines outside table and source regions
On Wed, Sep 22, 2021 at 3:49 PM Bill Burdick wrote: > > How about adding > > (lambda () (toggle-truncate-lines 1)) > > to org-mode-hooks in your EMACS init file? isn't this the same as M-x toggle-truncate-lines ? Because it will truncate every line, but I'm searching for a way to truncate only text, and not tables nor code. AM I misunderstanding your suggestion? Luca
Re: Heading toward Org 9.5
Yasushi SHOJI writes: > On Wed, Sep 22, 2021 at 5:21 PM Pankaj Jangid wrote: >> Is there a page where I can see the changes when moving from 9.4 to >> 9.5. > > Like etc/ORG-NEWS ? > http://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/etc/ORG-NEWS > > You can see it on the web but it's much more present to use Org Mode > for obvious reasons. Thanks for sharing this, Yasushi. Because I use the bundled Org, online version is the only option at present. :-). But I’ll definitely refer to this file from next week onwards, after 9.5 release. -- Regards ~Pankaj
