Re: [O] Something like #+BIND but for the destination buffer
/s/indention/indentation/ And sorry for the earlier top-posting and generally awful formatting. For some odd reason I subscribed using Gmail, and that is giving me some grieve. On Sat, Jan 14, 2017 at 11:11 PM, Jonas Bernoulliwrote: > On Sat, Jan 14, 2017 at 6:52 PM, Nicolas Goaziou > wrote: >> >> >> Could you show an ECM? >> > > I was going to, but: > > Turns out: > 1. Whether -i is used doesn't matter here. > 2. The reason these blocks are not intended the same way is that >SRC => @example or @lisp >EXAMPLE => @verbatim > 3. What bothered me wasn't so much the additional indention, but the > inconsistency. I actually like it better with the extra indentation, and I > also think that this is what we are suppposed to do in Texinfo. So I am > redefining org-texinfo-example-block to use @example instead of @verbatim. > > Best regards, > Jonas > >
Re: [O] Something like #+BIND but for the destination buffer
On Sat, Jan 14, 2017 at 6:52 PM, Nicolas Goaziouwrote: > > > Could you show an ECM? > I was going to, but: Turns out: 1. Whether -i is used doesn't matter here. 2. The reason these blocks are not intended the same way is that SRC => @example or @lisp EXAMPLE => @verbatim 3. What bothered me wasn't so much the additional indention, but the inconsistency. I actually like it better with the extra indentation, and I also think that this is what we are suppposed to do in Texinfo. So I am redefining org-texinfo-example-block to use @example instead of @verbatim. Best regards, Jonas
Re: [O] Something like #+BIND but for the destination buffer
On Sat, Dec 31, 2016 at 3:40 PM, Nicolas Goaziouwrote: Besides, using `org-export-filter-final-output-functions' seems easier > than your set up. > This approach works too. The following code produces exactly the same result as what I posted earlier: (defun ox-texinfo+--untabify (string back-end _) (if (eq back-end 'texinfo) (replace-regexp-in-string "^\t+" (lambda (match) (make-string (* (length match) 8) ?\s)) string) string)) (add-to-list 'org-export-filter-final-output-functions 'ox-texinfo+--untabify)
Re: [O] A summary with weekly processed actions using org-todo
Hi Yann, > My life is relying on orgmode, from a personal standpoint (orgmode is > faster at reminding me pending actions to fix my house than my wife) > and to organize my actions at work pushing my mutt mails in org-mode > as tasks... all this works great. Special thanks to the team for this > superb work. > > I was wondering if there was a way to help me in sorting tasks. I have > many actions/tasks during the week to process, some are done, some are > waiting for feedbacks... on Mondays, I would like to generate a > summary of the few actions that I changed the status during the last > n-days (week, month...). I checked the Worg and other places but was > not able to find the trick. > > I'm pretty sure somebody had this need before but am not able to find > the answer. You may find some inspiration at the custom Org views I built in https://github.com/fniessen/emacs-leuven/blob/master/org-leuven-agenda-views.txt (literate programming file -- needs tangling). The views are more for daily/weekly usage, but you could make them run over a month by customizing them to your taste... -- Best regards, Fabrice Niessen Leuven, Belgium http://www.pirilampo.org/
Re: [O] Something like #+BIND but for the destination buffer
I'll get back to you in a few days. On Sat, Jan 14, 2017 at 6:52 PM, Nicolas Goaziouwrote: > Jonas Bernoulli writes: > > > I did notice myself that the two-space indentation for blocks that are > part > > of a list element are reserved and also that one can do what you are > > suggesting here to keep the code-block as part of the list item while at > > the same time not get those two extra spaces. (By the way, I don't like > > that work-around.) > > This is not really a work-around. If we want to preserve indentation, as > "-i" implies, we need a fixed point to compute it. Here it is column 0. > > > However for me that's what happened for example blocks only. For source > > blocks I got an additional five spaces, for which I found no explanation. > > (The only indentation in the Org source before the code-block lines are > the > > two part-of-a-list-element spaces.) > > Could you show an ECM? > > Regards, >
Re: [O] Emacs hangs sometimes for no reason
fwiw, i have had the element cache turned off since org 8 because of intermittent bugs. i tried it on in org 9 maint recently and it caused similar problems. so you might be experiencing same. funnily enough, it doesn't seem to make any difference to agenda creation speed, which is my bottleneck. >> My actual question is, had someone had similar issues? Or is it just me >> with my configuration?
[O] Switching buffers from babel snippets
Hi, I've trying to further automate my maintainer tasks by moving things into babel snippets. I have one to find a cover letter and edit the file: #+name: edit-cover-letter #+begin_src emacs-lisp :var cover=create-qemu-pull[0] (find-file (expand-file-name (concat default-directory (car cover (mail-mode) #+end_src However when I run the code although the file is loaded and in the right mode I never see the buffer come up and have to switch to it manually. I expect this is because the code is running under some sort of safe-excursion. Is there anyway to pass a final buffer back to org-mode after the code is run and switch to it? -- Alex Bennée
Re: [O] Emacs hangs sometimes for no reason
Hello, Sebastian Christwrites: > in the last couple weeks (perhaps months?) Emacs hangs for no specific > reason for me. The single constant is, that when it hangs, it hangs > while I'm in org-mode. This occurs on multiple circumstance as > > - changing the outline structure by demoting and promoting headline > - when refiling > - re-schedule in agenda > - yanking > - perhaps more > > The strange thing is that it happens unpredictably, e.g. I re-schedule > 11 items without problems and the 12th one lets Emacs crash. Sometimes > it works for days without problems and then I promote a headline and > Emacs crashes. Very sad :( > > When I kill Emacs with > > $ pkill -SIGUSR2 Emacs > > this leaves me in the Emacs debugger in a flyspell function or (today) > in a avl-tree function. > > My actual question is, had someone had similar issues? Or is it just me > with my configuration? > > Perhaps someone can guide me on how I can find the root cause for this? > I pretty much lost here. This could be related to Org cache. I know the cache can become corrupted upon modifying outline structure of a document. Unfortunately, I couldn't come with a small enough recipe to reproduce the exact problem. You could try to set `org-element-use-cache' to nil and see if the hangs disappear. Regards, -- Nicolas Goaziou
Re: [O] Bug: Problem with org-agenda-sticky and org-mobile
Nicolas Goaziouwrites: > Hello, > > Ian Dunn writes: > >> With trunk org mode, when I run org-mobile-push when in an agenda >> buffer, then refresh the buffer (via 'r' or 'g'), it spawns a new >> agenda buffer and populates it. This only happens with >> org-agenda-sticky set to 't'. >> >> To replicate, I do the following: >> >> 1. Turn on org-agenda-sticky >> 2. Activate an agenda (any agenda) >> 3. Run org-mobile-push >> 4. Press 'r' after it's finished >> >> On mine, it spawns a new agenda buffer. This is not the behavior I'd >> expect. >> >> It looks to me like this is an issue in org-mobile-push. It sets >> org-agenda-this-buffer-name to the original value of org-agenda-buffer-name, >> which isn't necessarily the same. >> >> Thanks for your help. > > I pushed a fix for this. Could you confirm the problem is solved? Thank > you. > > > Regards, That fixed it. Thank you. -- Ian Dunn
[O] Emacs hangs sometimes for no reason
Hi list, in the last couple weeks (perhaps months?) Emacs hangs for no specific reason for me. The single constant is, that when it hangs, it hangs while I'm in org-mode. This occurs on multiple circumstance as - changing the outline structure by demoting and promoting headline - when refiling - re-schedule in agenda - yanking - perhaps more The strange thing is that it happens unpredictably, e.g. I re-schedule 11 items without problems and the 12th one lets Emacs crash. Sometimes it works for days without problems and then I promote a headline and Emacs crashes. Very sad :( When I kill Emacs with $ pkill -SIGUSR2 Emacs this leaves me in the Emacs debugger in a flyspell function or (today) in a avl-tree function. My actual question is, had someone had similar issues? Or is it just me with my configuration? Perhaps someone can guide me on how I can find the root cause for this? I pretty much lost here. Thanks in advance for any hints. Best, Sebastian -- Sebastian (Rudolfo) Christ http://rudolfochrist.github.io GPG Fingerprint: 306D 8FD3 DFB6 4E44 5061 CE71 6407 D6F8 2AC5 55DD
Re: [O] Something like #+BIND but for the destination buffer
Jonas Bernoulliwrites: > I did notice myself that the two-space indentation for blocks that are part > of a list element are reserved and also that one can do what you are > suggesting here to keep the code-block as part of the list item while at > the same time not get those two extra spaces. (By the way, I don't like > that work-around.) This is not really a work-around. If we want to preserve indentation, as "-i" implies, we need a fixed point to compute it. Here it is column 0. > However for me that's what happened for example blocks only. For source > blocks I got an additional five spaces, for which I found no explanation. > (The only indentation in the Org source before the code-block lines are the > two part-of-a-list-element spaces.) Could you show an ECM? Regards,
Re: [O] Something like #+BIND but for the destination buffer
I did notice myself that the two-space indentation for blocks that are part of a list element are reserved and also that one can do what you are suggesting here to keep the code-block as part of the list item while at the same time not get those two extra spaces. (By the way, I don't like that work-around.) However for me that's what happened for example blocks only. For source blocks I got an additional five spaces, for which I found no explanation. (The only indentation in the Org source before the code-block lines are the two part-of-a-list-element spaces.) On Sat, Jan 14, 2017 at 3:46 PM, Nicolas Goaziouwrote: > Hello, > > Jonas Bernoulli writes: > > > This seemed promising at first but let to all kinds of strange behavior. > > Code-blocks that are part of a list item turned out to particularly > > painful, as here "Finally, you can use ‘-i’ to preserve the indentation > of > > a specific code block" means that an additional five (if I remember > > correctly) spaces appear out of nowhere (only for code-blocks, > > example-blocks behaved as expected (or at least in an reasonable > > way)). > > With -i, indentation is taken from column 0, so the five spaces didn't > come out of nowhere, but probably from the indentation you gave to the > contents of the source block, which is not necessary. E.g., > > - Some list item > > #+BEGIN_SRC emacs-lisp -i > This is the code, and it will not break list > #+END_SRC > > > Regards, > > -- > Nicolas Goaziou >
Re: [O] Fwd: Beamer framebreak
On Sat, Jan 14, 2017 at 12:36 AM,wrote: > Hello eric, > [snip] > Mmm... I think that this would mess up my outline. Is there a way to create > an empty headline? or to hide it in the TOC? > >> Blocks are 3rd level headlines so put the contents within a 3rd level >> headline. > > I think that I will have to work with my outline options or something too. > > Thanks a lot! Sorry for being so noob! > This list is amazing and very happy to help; that said, text/email is clearly difficult to use when trying to "design" or communicate graphics layout. What if you created something like 3-5 slides or something in a different program representing quickly what you want, or even type it out in plain text? Slide 1: title slide Slide 2: TOC which will contain the titles of the slides listed shown indented under each section Section 1: blah Slide 3: introduction - will contain bullets and an image Maybe that's not much clearer, but wanted to lower the barrier in case you don't want to make a graphical example :) I think that's best... namely "Here's what I want, here's what I'm trying in org. I don't understand why it isn't working." Then we can quickly compare and point you in the right direction. Thanks! John > > > - > > ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the > NSA's hands! > $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No > bandwidth quotas! > Commercial and Bulk Mail Options!
Re: [O] Bug: Problem with org-agenda-sticky and org-mobile
Hello, Ian Dunnwrites: > With trunk org mode, when I run org-mobile-push when in an agenda > buffer, then refresh the buffer (via 'r' or 'g'), it spawns a new > agenda buffer and populates it. This only happens with > org-agenda-sticky set to 't'. > > To replicate, I do the following: > > 1. Turn on org-agenda-sticky > 2. Activate an agenda (any agenda) > 3. Run org-mobile-push > 4. Press 'r' after it's finished > > On mine, it spawns a new agenda buffer. This is not the behavior I'd > expect. > > It looks to me like this is an issue in org-mobile-push. It sets > org-agenda-this-buffer-name to the original value of org-agenda-buffer-name, > which isn't necessarily the same. > > Thanks for your help. I pushed a fix for this. Could you confirm the problem is solved? Thank you. Regards, -- Nicolas Goaziou
Re: [O] Something like #+BIND but for the destination buffer
Hello, Jonas Bernoulliwrites: > This seemed promising at first but let to all kinds of strange behavior. > Code-blocks that are part of a list item turned out to particularly > painful, as here "Finally, you can use ‘-i’ to preserve the indentation of > a specific code block" means that an additional five (if I remember > correctly) spaces appear out of nowhere (only for code-blocks, > example-blocks behaved as expected (or at least in an reasonable > way)). With -i, indentation is taken from column 0, so the five spaces didn't come out of nowhere, but probably from the indentation you gave to the contents of the source block, which is not necessary. E.g., - Some list item #+BEGIN_SRC emacs-lisp -i This is the code, and it will not break list #+END_SRC Regards, -- Nicolas Goaziou
Re: [O] Something like #+BIND but for the destination buffer
Thanks for the tip and sorry for the late response. This seemed promising at first but let to all kinds of strange behavior. Code-blocks that are part of a list item turned out to particularly painful, as here "Finally, you can use ‘-i’ to preserve the indentation of a specific code block" means that an additional five (if I remember correctly) spaces appear out of nowhere (only for code-blocks, example-blocks behaved as expected (or at least in an reasonable way)). I am going to use the `org-export-filter-final-output-functions` approach suggested earlier. I might at a later time come back here to discuss the issues I encountered, but right now I am too frustrated about the difficulties I encountered to do so. (Texinfo is painful enough to deal with, if now Org (resp. its texinfo exporter) also acts up, that's just to much to take.)
Re: [O] Fwd: Beamer framebreak
Hello eric, Your org file layout is a little confused. You have told org that beamer slides (aka frames) will be level 2 headlines (so level 1 headlines become sections). Then you, for instance, some content directly under a level 1 headline which is ignored. Third level headlines will become blocks within a frame. Oh, I didn't know that I could not put raw text after a headline in ox-beamer. Thanks. Currently, it is part of the "Structure and Function" slide because your figures are within a level 3 headline which is converted to a block. Put the figures under a second level headline instead. Mmm... I think that this would mess up my outline. Is there a way to create an empty headline? or to hide it in the TOC? Blocks are 3rd level headlines so put the contents within a 3rd level headline. I think that I will have to work with my outline options or something too. Thanks a lot! Sorry for being so noob! - ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!
Re: [O] org-get-heading and COMMENT
Hello, Matt Pricewrites: > I see that > > (org-get-heading t t) > > executed on a heading like: > > * COMMENT Heading Title > > returns: > > COMMENT Heading Title > > Should there be a third switch, something like NO-COMMENT? I have no objection, but it would also need to have NO-PRIORITY for completeness. Do you want to provide a patch for that? Regards, -- Nicolas Goaziou