[O] Release 9.2.6
Hi all, I released Org 9.2.6, a bugfix release. Enjoy! -- Bastien
Re: [O] Move Currently clocked in task to left on modeline
Thanks Nick, Anyone else, I would like to hear how you can keep the currently clocked task in plain site - I use MacOS and Linux, so if there's any OS-specific status software that you recommend let me know. Thanks, --Nate On Mon, Jul 22, 2019 at 6:39 PM Nick Dokos wrote: > Nathan Neff writes: > > > Hello all, > > > > How can I move the currently clocked task to be on the left side > > of my modeline in emacs? > > > > The way the information ends up in the mode line is a bit convoluted: > > - The main variable is `mode-line-format': you should read its doc > string carefully. > > - `mode-line-format' includes the variable `mode-line-misc-info' > towards the end. > > - `mode-line-misc-info' includes the variable `global-mode-string' > (in a somewhat peculiar way that I don't quite understand). > > - `org-clock-in', `org-clock-out' and `org-clock-cancel' affect the > mode line by modifying the `global-mode-string' variable to append > or delete `org-mode-line-string' to/from it and then forcing a > mode-line update with (drum roll) `force-mode-line-update'. > > - The rest of the org mode code mucks around with `org-mode-line-string' > exclusively. > > In short, there is no way to change the position of the currently > clocked task without rewriting code. You might be able to move > *all* of the org information by modifying an earlier mode-line > component (rather than `global-mode-string' which is part of the > final component). But it would not be trivial. > > -- > Nick > > "There are only two hard problems in computer science: cache > invalidation, naming things, and off-by-one errors." -Martin Fowler > > >
Re: [O] git-annex-related org-attach tests failing on master
Gustav Wikström writes: > I've taken a look and have fixed the issues on my > local machine. Thank you! > I must say the whole git-annex thing feels misplaced in the > Org mode repository though. I guess, as long as git annex isn't installed > it's not really an issue. But it surely would fit better as a separate > library. I'm a heavy git-annex user, but I haven't done more than play with org-attach (a while back), so I don't have much of an opinion here, but your general assessment sounds fair. That being said, the org-attach/git-annex functionality has been around since 2012, so provided it's not making other things more difficult, moving it outside of Org doesn't seem worth the effort or disruption of people's workflows. Thanks again for looking into the failures. -- Kyle
[O] sql code block #+BEGIN_SRC sql :tangle qry/testthis.sql :cmdline "-v this=\\'asdf\\'"
I am surprised by the level of quoting seemingly required by org-mode to pass a variable to psql in :cmdline The following works: #+PROPERTY: header-args:sql :engine postgresql :dbhost my.host :database mydb :dbuser me #+PROPERTY: header-args:sql+ :tangle no :results table :exports both #+BEGIN_SRC sql :cmdline "-v this=\\'that\\'" select :this as this #+END_SRC #+RESULTS: | this | |--| | that | However, I found no other quote/escape combination to work. At first I expected to work: :cmdline "-v this=\'asdf\'" ... but it is an error. Is this expected and consistent with other emacs behavior? Is there another, perhaps simpler, way to pass variables to postgresql code block in org ob-sql? Thanks, Malcolm
[O] [Performance] org-indent-mode slows down checklists
Reproduction steps: 1. emacs -Q 2. (progn (end-of-buffer) (insert "* Section [0/0]\n") (dotimes (n 150 nil) (insert "- [ ] item\n")) (org-mode)) 3. Try C-c on an item 4. turn on (org-indent-mode) and C-c gets noticably slow(er) Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.2/lisp/org/) Emacs 26.2 Regards, Dmitrii
Re: [O] Bug: org-edit-src keeps splitting the window [9.2.5 (release_9.2.5-504-g3c24be @ /home/immanuel/.emacs.d/straight/build/org/)]
Hello, Immanuel Litzroth writes: > You want me to do that and send a new patch or are you going > to do it after you apply the patch? The former, if you don't mind. Regards, -- Nicolas Goaziou
Re: [O] Duplicate tags
BTW one possible behavior is to move the old tag to the end, providing both feedback and function вт, 3 сент. 2019 г. в 16:29, Dmitrii Korobeinikov : >org-set-tags-command allows duplicates. Example: >- M-x org-set-tags-command -> "tag" >- M-x org-set-tags-command -> "tag" >Result: >* Title:tag:tag: > >I think it would be handy to prevent this. >Not unimaginable that someone could use this as a feature, though, in > which case, a flag would be nice. > >Regards, >Dmitrii. >
[O] Duplicate tags
org-set-tags-command allows duplicates. Example: - M-x org-set-tags-command -> "tag" - M-x org-set-tags-command -> "tag" Result: * Title:tag:tag: I think it would be handy to prevent this. Not unimaginable that someone could use this as a feature, though, in which case, a flag would be nice. Regards, Dmitrii.
Re: [O] Disallow empty tags
Am 02.09.19 um 18:48 schrieb Dmitrii Korobeinikov: > Creating an empty tag renders TAB-completion useless. > > Example: > > * Title :a::b: > > Pressing TAB in org-set-tags-command will now insert a colon `:`, which > is quite puzzling to see. > I thought something was wrong w/ my bindings till I noticed this was > happening only in one of my files. > > Can such tags be ignored/disallowed as they hold no evident purpose? I vote for ignored, because there's places where tag lists are displayed like that, making newbies think that's valid syntax. Where that happens? I have a file with a filetag R and a todo entry with a tag :V: . In the agenda, that entry's tags are shown as :R::V: . Yours, Julius
Re: [O] Disable typo-mode in org source code blocks
On Mon 02-Sep-2019 at 20:26:22 +02, John Kitchin wrote: > You can use cursor-sensor mode for this if you have emacs 26ish. The idea is > you set cursor-sensor functions on a region that do something depending on > whether you enter or leave the region. Below, I tie into > the org font lock mechanisms to add these properties so that when you enter, > typo mode gets turned off, and when you leave it gets turned back on. I use a > similar approach to put src-block specific key maps > on src blocks. There are two examples of functions that are "lightly tested". > I can see why you would want this disabled in src blocks, it never puts the > right quote in! > […] Hi, Thanks for this! I will have to spend some time before I understand everything, but this is of great help. --
