Re: [O] Visualizing org files
Oh wow Karl, lot's of 'hidden' gems there. Not related to this thread but I specially liked `lazyblorg`, I actually had a very similar idea and was about to develop something like that, you saved me a bunch of time :) On Mon, Oct 1, 2018 at 3:57 PM Samuel Wales wrote: > market more :] > > or you could convert it to an emacs visualization in the agenda buffer :] > >
Re: [O] Branch "next" garbled
Am 03.10.18 um 13:45 schrieb Marco Wahl: > My git fu was not strong enough and so the "next" branch is a bit messy > right now. (I tried to activate a local clean version of the "next" > branch.) > > I thought I could easily rollback the mess I created by going back to > the git node 3c8fd4fa7 which is the last git node before my activities. > > The command I used is > > git revert 3c8fd4fa7 > > Unfortunately this did not revert the repo to that node. To make your git fu a bit stronger, let me explain this: 'git revert' creates a new commit, that reverses the changes from the given commit, so it's not, what you have had in mind (and what is common for SCMs like SVN where you cannot rewrite the history). You are looking for 'git reset': https://git-scm.com/book/en/v2/Git-Tools-Reset-Demystified There are other ways, to achieve the same result: Just rename the branch and checkout a new one with the old name at the given commit. That gives you a nice backup for free. Or utilize the 'reflog': http://gitready.com/intermediate/2009/02/09/reflog-your-safety-net.html Hope this helps Uwe
Re: [O] Branch "next" garbled
>> My git fu was not strong enough and so the "next" branch is a bit messy >> right now. (I tried to activate a local clean version of the "next" >> branch.) >> [...] >> Can someone help to clean up the "next" branch, please? > > I think I cleaned it. Thank you so much! > To prevent further complications with this branch, I suggest to treat is > like master and master like maint. I.e., every commit done in master is > duplicated into next so that final merge is easier. > WDYT? This is a clear rule, which is easy to follow and easy to remember (at least for me). I love this! Thanks and best regards, Marco
[O] bug#32846: 26.1; Table with links of different lengths break tabbing
Hello, Christoph Michelbach writes: > I noticed that a table as attached to this email (also available here: > https://p > astebin.com/AG7pwcq1) breaks org-mode's automatic adjustment of tables when > pressing tab. > > To reproduce the problem, simply follow these steps: > 1. Load the file and load org-mode. Point is at the beginning of the file. > 2. Press tab. Point moves to the beginning of the word "filename" in the top > left cell. > 3. Press tab again. The table is now broken. This bug is fixed in a recent Org. You need to wait for a new release. I'm closing this bug. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Branch "next" garbled
Hello, Marco Wahl writes: > Hello fellow Orgers, > > This is more an internal issue about the repo and in particular the > "next" branch. > > My git fu was not strong enough and so the "next" branch is a bit messy > right now. (I tried to activate a local clean version of the "next" > branch.) > > I thought I could easily rollback the mess I created by going back to > the git node 3c8fd4fa7 which is the last git node before my activities. > > The command I used is > > git revert 3c8fd4fa7 > > Unfortunately this did not revert the repo to that node. > > Can someone help to clean up the "next" branch, please? I think I cleaned it. To prevent further complications with this branch, I suggest to treat is like master and master like maint. I.e., every commit done in master is duplicated into next so that final merge is easier. WDYT? Regards, -- Nicolas Goaziou
Re: [O] HTML Export - Footnotes inconcistency
Hello, Matthias Paulmier writes: > I think I get the logic behind it. The problem is the inconsistency it > creates for the viewer. Does it really matter for them if I wrote my > footnote inline or not? Inline footnotes are now wrapped within a paragraph. Thank you. Regards, -- Nicolas Goaziou
Re: [O] How about lifting the limit of 35 tasks in org-clock-history?
On 2018-10-03, at 12:51, Nicolas Goaziou wrote: > Hello, > > Marcin Borkowski writes: > >> I attach a patch with a more verbose docstring. >> >> It is perhaps still not ideal - in particular, the warning is not >> visible in the Customize interface - but I do not think this is a big >> deal. My line of thinking is that: >> >> - if a user wants to change this setting, they will either look up the >> docstring and understand the limitation (btw, even the built-in way >> works for org-clock-history-length as high as 76 or so, provided you >> have a really high frame), or >> >> - use Customize, which is potentially a trouble - but in that case, >> I would assume that the user fiddles with org-clock-history-length >> because they clock in many tasks, and then they will see that the list >> in the *Clock Task Select* buffer is too long anyway, and dial the >> setting down. > > It sounds good. I applied your patch. Thank you. Thanks, too! (Also for your extremely fast reply, comparing to my one;-).) Best, -- Marcin Borkowski http://mbork.pl
[O] Branch "next" garbled
Hello fellow Orgers, This is more an internal issue about the repo and in particular the "next" branch. My git fu was not strong enough and so the "next" branch is a bit messy right now. (I tried to activate a local clean version of the "next" branch.) I thought I could easily rollback the mess I created by going back to the git node 3c8fd4fa7 which is the last git node before my activities. The command I used is git revert 3c8fd4fa7 Unfortunately this did not revert the repo to that node. Can someone help to clean up the "next" branch, please? Thanks and apologies, -- Marco
Re: [O] How about lifting the limit of 35 tasks in org-clock-history?
Hello, Marcin Borkowski writes: > I attach a patch with a more verbose docstring. > > It is perhaps still not ideal - in particular, the warning is not > visible in the Customize interface - but I do not think this is a big > deal. My line of thinking is that: > > - if a user wants to change this setting, they will either look up the > docstring and understand the limitation (btw, even the built-in way > works for org-clock-history-length as high as 76 or so, provided you > have a really high frame), or > > - use Customize, which is potentially a trouble - but in that case, > I would assume that the user fiddles with org-clock-history-length > because they clock in many tasks, and then they will see that the list > in the *Clock Task Select* buffer is too long anyway, and dial the > setting down. It sounds good. I applied your patch. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Subject: Bug: Confusing documentation for org-complete-tags-always-offer-all-agenda-tags [9.1.14 (9.1.14-1-g4931fc-elpaplus @ /home/n/.emacs.d/elpa/org-plus-contrib-20180917/)]
Hello, > That aside, the wording of the second sentence could be clearer. > My humble suggestion: > > "If non-nil, always offer completion for all tags of all agenda files. > Setting this variable locally allows for dynamic generation of tag > completions in capture buffers." Applied. Thank you. Regards, -- Nicolas Goaziou
[O] bug#32906: org-in-src-block-p always returns nil
Eivind Otto Hjelle writes: > I thought I had updated emacs to the latest version, but apparently not. > After upgrading to emacs-26 the command org-in-src-block-p works as > expected. Thanks! Thanks for checking. Closing. Regards Robert
Re: [O] [ANN] org-info-find-node: Jump from Org to specific Info
>> I just pushed command `org-info-find-node' bound to "C-c C-x I" by >> default for Org files and agenda buffers. > > Nitpick: Would you mind removing the dangling parens left in the > function? Okay, thanks. Consider it DONE. > Also, I'd like to avoid making changes to "master" branch. It should be > considered frozen while we're waiting for Org 9.2. Please install next > new features (that one is OK, I guess) in "next" branch, and rebase it > on top of "master". Okay for the next feature I'll use the "next" branch. It might be worth the effort to document the role of the "next" branch somewhere. Ciao, -- Marco
Re: [O] Org mode + Solid = collaborative, privacy-respecting future
I would also like to see something developped in ths direction. Karl Voit writes: > Hi! > > I stubled over Tim Berners-Lee Solid: > https://www.fastcompany.com/90243936/exclusive-tim-berners-lee-tells-us-his-radical-new-plan-to-upend-the-world-wide-web > https://www.inrupt.com/blog/one-small-step-for-the-web > https://en.wikipedia.org/wiki/Solid_(web_decentralization_project) > > On https://github.com/solid/solid-apps I'd like to see something > that combines the awesome (local) power of Org mode with the > privacy-respecting soon-to-be platform Solid which adds > collaborative notions to the story. > > Are there any actions going on already? > > This just feels right to be combined with the power of Org/Emacs. -- Luke, use the FOSS Sent from Emacs
[O] Subject: Bug: Confusing documentation for org-complete-tags-always-offer-all-agenda-tags [9.1.14 (9.1.14-1-g4931fc-elpaplus @ /home/n/.emacs.d/elpa/org-plus-contrib-20180917/)]
The documentation for org-complete-tags-always-offer-all-agenda-tags
currently reads:
"If non-nil, always offer completion for all tags of all agenda files.
Instead of customizing this variable directly, you might want to
set it locally for capture buffers, because there no list of
tags in that file can be created dynamically (there are none)."
It appears the second sentence is missing a few words.
"...Instead of customizing this variable directly, you might want to
set it locally for capture buffers, because there *is* no list of
tags in that file *that* can be created dynamically (there are none)."
That aside, the wording of the second sentence could be clearer.
My humble suggestion:
"If non-nil, always offer completion for all tags of all agenda files.
Setting this variable locally allows for dynamic generation of tag
completions in capture buffers."
Thanks for your time,
no wayman
Emacs : GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.1)
of 2018-09-24
Package: Org mode version 9.1.14 (9.1.14-1-g4931fc-elpaplus @
/home/n/.emacs.d/elpa/org-plus-contrib-20180917/)
current state:
==
(setq
org-duration-format '(("h") (special . 2))
org-src-mode-hook '(doom-modeline-set-special-modeline
org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-refile-targets '((org-agenda-files :tag . "org-agenda-files")
(org-agenda-files :maxlevel . 20) (my/org-files-list
:maxlevel . 20))
org-enforce-todo-dependencies t
org-src-tab-acts-natively t
org-agenda-files '("~/Documents/todo")
org-reveal-start-hook '(org-decrypt-entry)
org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent)
org-mode-hook '(my/yas-hook org-bullets-mode writegood-mode
org-indent-mode flyspell-mode
(closure (t) nil (add-hook 'after-save-hook
'my/org-agenda-redo-all nil t))
#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook org-show-block-all
append local] 5]
#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook
org-babel-show-result-all append local]
5]
org-babel-result-hide-spec org-babel-hide-all-hashes
org-journal-update-auto-mode-alist org-eldoc-load)
org-outline-path-complete-in-steps nil
org-archive-hook '(org-attach-archive-delete-maybe)
org-journal-carryover-items nil
org-confirm-elisp-link-function 'yes-or-no-p
org-journal-mode-hook '(#[nil "\301 \302\303\304$\207"
[org-journal-encrypt-on org-add-hook
org-journal-encryption-hook
nil t]
5]
(lambda nil (auto-fill-mode t) (flyspell-mode t))
(lambda nil
(org-add-hook org-journal-encrypt-on
'org-journal-encryption-hook
nil t)
)
)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-bibtex-headline-format-function #[257 "\300 \236A\207" [:title] 3
"\n\n(fn ENTRY)"]
org-log-reschedule t
org-agenda-text-search-extra-files '(agenda-archives)
org-babel-pre-tangle-hook '(save-buffer)
org-file-apps '((auto-mode . emacs) ("\\.mm\\'" . default)
("\\.mp \\'" . "/usr/bin/mpv %s")
("\\.x?html?\\'" . "/usr/bin/firefox %s") ("\\.pdf\\'" .
default))
org-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-babel-load-languages '((js . t) (shell . t) (python . t) (org . t))
org-log-done 'time
org-journal-date-format "[%Y-%m-%d %a]"
org-hide-emphasis-markers t
org-ellipsis " ↴"
org-src-preserve-indentation t
org-fontify-done-headline t
org-occur-hook '(org-first-headline-recenter)
org-agenda-mode-hook '(org-journal-update-org-agenda-files)
org-structure-template-alist '(("x" "#+BEGIN_EXAMPLE\n?\n#+END_EXAMPLE")
("le" "#+BEGIN_SRC
emacs-lisp\n?\n#+END_SRC")
("s" "#+BEGIN_SRC ?\n\n#+END_SRC")
("e" "#+BEGIN_EXAMPLE\n?\n#+END_EXAMPLE")
("q" "#+BEGIN_QUOTE\n?\n#+END_QUOTE")
("v" "#+BEGIN_VERSE\n?\n#+END_VERSE")
("V" "#+BEGIN_VERBATIM\n?\n#+END_VERBATIM")
("c" "#+BEGIN_CENTER\n?\n#+END_CENTER")
("C" "#+BEGIN_COMMENT\n?\n#+END_COMMENT")
("l" "#+BEGIN_EXPORT
latex\n?\n#+END_EXPORT")
("L" "#+LaTeX: ")
("h" "#+BEGIN_EXPORT
