Re: [O] A mail client that is org-mode compatible
Hi Gour, Gour g...@atmarama.net writes: Afaict, there is no support in orgmode for Claws mailer which I use for regular email, mailing lists (mostly via gmane) as well as rss reader. But you're not alone in the Org/Claws desert: http://lists.gnu.org/archive/html/emacs-orgmode/2010-10/msg00539.html The function quote in the mail above could easily be enhanced to call Claws asynchronously. is Gnus the only Emacs-based client which has good support for all of these as well as good support for orgmode? AFAIK yes. You can create tasks from Mew/WL/MH-E/Rmail but Gnus is the only one to support org+nntp+rss. I'd also like to use Notmuch for quick searching and would fetch mail via getmail and use locally running dovecot for serving IMAP... Yesterday I read a bit about mu(4e), but it seems it handles only email and not nntp? Yes. HTH, -- Bastien
Re: [O] Bug: Table export to [tc]sv doesn't convert \vert [7.8.11]
Hi Nathan,
Nathan Trapuzzano nbt...@nbtrap.com writes:
Of course the particular implementation will have to be seen before it
can be accepted, but I'd like to get the spec accepted (provisionally)
before setting to work on it.
As a start, you can look at the way org-e-*.el backend export tables,
(use `org-e-ascii-table-cell' as an entry point). What we need is a
callback function to convert entities in cells, in org-export.el.
Since we already have org-entities, I would use it together with
`org-entity-get-representation' to convert entities from the \vert{}
representation to the | character (in the ASCII backend.)
Here's what I propose:
1. Do away with \vert{} entirely, leaving just \vert as an escape
sequence standing for |, no matter where it appears. \vert{}
unnecesarily complicates things, in my opinion.
Better to rely on org-entities and the way entities are treated so far.
2. The escape sequence must itself be escapable, wherefore I propose
to give the backslash special meaning in front of the string
vert. Specifically:
a. An even number of consecutive backslashes followed by vert
stands for that number of backslashes divided by two followed by
vert.
b. An odd number of consecutive backslashes followed by vert
stands for that many backslashes integer-divided by two, followed by
|.
For example, \vert exports to |, \\vert to \vert, \\\vert to
\|, vert to \\vert, and so on. Obviously, upon importing,
the reverse of the above will be carried out.
I would not take that route -- from experience, escaping espace
sequences can drive you mad, and all this is not intuitive for users.
I would simply convert entities by default and use a special table
cookie in lines where you do not want the conversion to happen.
For example:
| Header 1 | Header 2 |
|--+--|
| \vert{} | ABC |
= convert to |
But:
| | Header 1 | Header 2 |
|---+--+--|
| \ | \vert{} | ABC |
Don't convert. The \ char is free and a good choice here.
--
Bastien
Re: [O] Visibility cycling of plain lists?
Hi James, James Harkins jamshar...@gmail.com writes: http://orgmode.org/manual/Plain-lists.html#Plain-lists For more details, see the variable org-cycle-include-plain-lists. If this variable is set to integrate, plain list items will be treated like low-level headlines. This confused me, however, because there is no integrate option in org 7.9. There is an option As children of outline headings. You are confusing the value of the option (which can indeed be 'integrate as a symbol) and the description of this choice in the customize interface. I reread the docstring of this option and I think it's fine. Also, org-cycle-include-plain-lists's docstring is wrong: When t, make TAB cycle visibility on plain list items. Mhh... what is wrong here? So... never mind the original question (but there are a couple of documentation issues). Please report them as bugs in separate threads so that we can handle them. Thanks! -- Bastien
Re: [O] Bug: In list with checkboxes, meta-RET should add a checkbox for the next entry. [7.9.2 (7.9.2-dist @ /usr/share/emacs/site-lisp/org/)]
Hi Brian, Brian van den Broek brian.van.den.br...@gmail.com writes: So, I think that it would be more useful were M-RET to create a new item that has or does not have a checkbox present depending on whether it is invoked in a plain list item with or without a checkbox. Likewise S-M-RET could differ from the item at which is called with respect to checkbox presence. The downsides are this behaviour is more complex and likely would disturb some orgers' muscle memories. So, I'm not pushing hard but throwing it out there to see if it sticks :-) I tend to agree, but you'd have to convince users that M-RET should also insert TODO keywords when creating new headlines, which is not as obvious I think. -- Bastien
Re: [O] [PATCH] org-protocol: Pass optional value using query in url to capture from protocol.
Hi Ryo, I'm willing to apply this patch but since you already submitted tiny changes we would need to have you sign the FSF copyright assignment. See http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future.txt Let me know if you are willing to assign your copyright to the FSF. Thanks! -- Bastien
Re: [O] Trimming quotes
Hi Thomas, t...@tsdye.com (Thomas S. Dye) writes: As penance for my often low signal to noise ratio ;) and a small token of my appreciation for the Org community and its product, I've drafted a description of the mailing list for Worg, which AFAICT lacked one: http://orgmode.org/worg/org-mailing-list.html Thanks! And a happy new year too :) -- Bastien
Re: [O] Using Org-mode file format for storing configuration data
Hi Karl, Karl Voit devn...@karl-voit.at writes: I plan to implement a new weblog system that parses Org-mode files and generates (static) HTML output. Yes, I am aware that there are other solutions out there but I do not like them for various reasons.[1] It's always good to have new implementations -- looking forward to see this one happen! I have a plan to add a org-e-rss.el backend that would allow converting an Org file into a RSS feed. Together with a more clever org-publish.el, this could be used as a simple blog by updated the RSS feed depending on what new headlines have been published. This would suits most of my own needs, and it's not that much work... Just to let you know. Best, -- Bastien
[O] Multiple notions for what's a day
Hello, For 6 weeks now, since the commit a00a7b2 of Toby, things have changed when generating clock tables. For example, instead of getting this (for some sample files I have): | File | Headline | Time | |---++---| | | ALL Total time | 30:19 | |---++---| | A.org | File time | 2:59 | |---++---| | B.org | File time | 2:30 | |---++---| | C.org | File time | 24:50 | (edited for the sake of simplicity) we do have, as of today: | File | Headline | Time| |---++-| | | ALL Total time | 1d 6:19 | |---++-| | A.org | File time | 2:59| |---++-| | B.org | File time | 2:30| |---++-| | C.org | File time | 1d 0:50 | That is, the presentation *default* has changed: it now displays big amounts of hours in days (of 24 hours). I don't welcome the change of the default as such -- as that could impact computations made on those figures; OK, that's not such a big deal --, but I clearly like the ability to generate such formats, much more readable. However, there is now a problem of interpretation for the value of days; until now, a day was valued as 8 hours... see `org-effort-durations': ╭ │ Its value is ((h . 60) │ (d . 480) -- 8 hours a day │ (w . 2400) -- 40 hours a week │ (m . 9600) │ (y . 96000)) ╰ In the current situation, you'd express days of 8 hours for the Effort property, but be presented with days of 24 hours for clocking display. Weird, no? I guess that the clock tables should use the values defined in `org-effort-durations' for their display. Or, at least, any other solution where a day has the same value when used for clock estimates and for clock reports... Just wanted to show a problem, and start a discussion on what should be done... Best regards, Seb -- Sebastien Vauban
[O] Org to RSS (was: Using Org-mode file format for storing configuration data)
* Bastien b...@altern.org wrote: Hi Karl, Hi! Karl Voit devn...@karl-voit.at writes: I plan to implement a new weblog system that parses Org-mode files and generates (static) HTML output. Yes, I am aware that there are other solutions out there but I do not like them for various reasons.[1] It's always good to have new implementations -- looking forward to see this one happen! Me too :-) I have a plan to add a org-e-rss.el backend that would allow converting an Org file into a RSS feed. Together with a more clever org-publish.el, this could be used as a simple blog by updated the RSS feed depending on what new headlines have been published. This would suits most of my own needs, and it's not that much work... Just to let you know. Great news! Although in my particular case, it will not be part of my solution - sadly :-( -- Karl Voit
Re: [O] A mail client that is org-mode compatible
On Mon, 31 Dec 2012 10:19:58 +0100 Bastien b...@altern.org wrote: But you're not alone in the Org/Claws desert: http://lists.gnu.org/archive/html/emacs-orgmode/2010-10/msg00539.html Yeah, I saw it, but not much afterwards. AFAIK yes. You can create tasks from Mew/WL/MH-E/Rmail but Gnus is the only one to support org+nntp+rss. I used Gnus in the past but had some rss parsing-related problems. Otoh, this might be good opportunity to return to Gnus and just keep some simple mailer for my other family members to access their mail. Yesterday I read a bit about mu(4e), but it seems it handles only email and not nntp? Yes. Then the Gnus is without competition. HTH, Yes. Thank you for your reply and taking care about orgmode. ;) Sincerely, Gour -- Many, many births both you and I have passed. I can remember all of them, but you cannot, O subduer of the enemy! http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature
Re: [O] Visibility cycling of plain lists?
On Dec 31, 2012 5:36 PM, Bastien b...@altern.org wrote: This confused me, however, because there is no integrate option in org 7.9. There is an option As children of outline headings. You are confusing the value of the option (which can indeed be 'integrate as a symbol) and the description of this choice in the customize interface. My point exactly- neither the manual nor the docstring do anything to dispel that confusion. Also, org-cycle-include-plain-lists's docstring is wrong: When t, make TAB cycle visibility on plain list items. Mhh... what is wrong here? There are (at least) 3 options (I have no idea if there are any more), but only t is described. I suppose t is the default behavior (tab collapses plain list items, but they're all open by default). But I'm guessing based on observation. This goes unstated. 'integrate is a valid option, but the docstring doesn't say so. It also doesn't say anything about the behavior of nil. I can file bugs later. hjh
Re: [O] Visibility cycling of plain lists?
Hi James, James Harkins jamshar...@gmail.com writes: My point exactly- neither the manual nor the docstring do anything to dispel that confusion. If you do C-h v org-cycle-include-plain-lists RET you read that a value of t allows visibility cycling and that a value of 'integrate temporarily interprets list items as outline headlines. When customizing, you can either set it to Never, which is obvious. Or to `t', which is explained. Or to the other value, which is the symbol 'integrate. This third value is mentioned in the docstring, and it is pretty obvious that it corresponds to As children of outline headings, as there are no other choices. There are (at least) 3 options (I have no idea if there are any more), but only t is described. No -- t and 'integrate are described. I suppose t is the default behavior It is -- and C-h v org-cycle-include-plain-lists RET tells you this. (tab collapses plain list items, but they're all open by default). But I'm guessing based on observation. This goes unstated. 'integrate is a valid option, but the docstring doesn't say so. Well, it does say so. It also doesn't say anything about the behavior of nil. I can file bugs later. Please make sure this is a real bug and not a misunderstanding on your side. Also please provide a patch, that's often the best way to understand where misunderstandings lie. Thanks! -- Bastien
[O] How to get a paper scanner into org-mode workflow
Hi, I plan to buy a document scanner with ADF and duplex function to scan all incoming/intermediate/outgoing papers, convert them into PDF and link those into my org-files. I was wondering if someone did something like this already? I use Linux and hence I am looking for a Linux friendly solution. On the web I found scanbuttond which enables to run a script if a scanner button is pressed and it seems scanning under Linux is rather scriptable. I want to make this finally as smooth, easy and painless as possible to make sure I do not pile up papers because I am to lazy to scan them on a day by day basis. Ideally, I want to fill the ADF unit, press a button, receive a single PDF with all pages scanned duplex in a preset folder, and keep a path to that file in org-modes killring to place it as a link at the right place. OCR would be nice too to get a full searchable system. I guess I am not the first one who tries this and I would be glad if people share there experience and set-ups. Thanks and happy new Year Torsten CC. Any recommendation on a well working scanner under Linux. At the moment my favorite is the Fujitsu ScanSnap S1500. Seems to work out of the box and comes with a good performance.
[O] org-goto bug
Hi,
According to the manual, and the help window that pops up when you call it,
org-goto should accept a few one-letter commands to move up one level (u),
quit (q), move to the next (n) or previous(p) heading.
However, whenever I try any of these keys, they are interpreted as the
search string for isearch. My set-up is provided below. I have confirmed
that this is also the case when I start emacs with 'emacs -Q', so I don't
think I've done this in my config.
Thanks,
Tyler
Emacs : GNU Emacs 24.3.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10)
of 2012-12-27 on ONOTTAR654746
Package: Org-mode version 7.9.1 (7.9.1-dist @
/usr/local/share/emacs/site-lisp/org/)
current state:
==
(setq
org-export-blocks '((src org-babel-exp-src-block nil)
(export-comment org-export-blocks-format-comment t)
(ditaa org-export-blocks-format-ditaa nil) (dot
org-export-blocks-format-dot nil))
org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
org-export-latex-packages-alist '(( natbib nil) \\bibpunct{(} {)} {;}
{a} {} {,})
org-reverse-note-order t
org-agenda-skip-scheduled-if-done t
org-export-with-drawers t
org-export-with-tags t
org-export-preprocess-before-selecting-backend-code-hook
'(org-beamer-select-beamer-code)
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-refile-targets '((my-org-refile-targets :maxlevel . 5))
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent)
org-babel-pre-tangle-hook '(save-buffer)
org-occur-hook '(org-first-headline-recenter)
org-export-interblocks '((src org-babel-exp-non-block-elements))
org-metaup-hook '(org-babel-load-in-session-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-export-latex-format-toc-function 'org-export-latex-format-toc-default
org-fast-tag-selection-single-key 'expert
org-default-notes-file ~/.emacs.d/org/notes.org
org-export-preprocess-before-normalizing-links-hook
'(org-remove-file-link-modifiers)
org-cycle-global-at-bob t
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-agenda-ndays 7
org-agenda-include-diary t
org-agenda-skip-deadline-if-done t
org-enforce-todo-dependencies t
org-export-first-hook '(org-beamer-initialize-open-trackers)
org-mode-hook '(my-org-mode-hook er/add-org-mode-expansions
#[nil \300\301\302\303\304$\207
[org-add-hook change-major-mode-hook org-show-block-all
append local]
5]
#[nil \300\301\302\303\304$\207
[org-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-agenda-start-on-weekday nil
org-directory ~/.emacs.d/org
org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc
org-beamer-auto-fragile-frames
org-beamer-place-default-actions-for-lists)
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-confirm-shell-link-function 'yes-or-no-p
)
Re: [O] org-mime-htmlize
Hi, Concerning: Bastien Hi George, thanks for reporting this. Bastien Eric Schulte schulte.e...@gmail.com writes: From cf2128fb320f714f78fa54b953405d01fa73bf33 Mon Sep 17 00:00:00 2001 From: Eric Schulte eric.schu...@gmx.com Date: Fri, 28 Dec 2012 08:20:56 -0700 Subject: [PATCH] Pass the dir option on through org-export-as-string * lisp/org-exp.el (org-export-string): Pass the dir option on through to any subsequent export functions. Bastien Applied, thanks! I waited for a new org-plus-contrib elpa package to try this... I installed the new one just now, and M-x org-mime-htmlize in a message buffer now gives a Wrong number of arguments error. Maybe I've done something boneheaded, but I can't work out what it is... Here is a backtrace: backtrace-dec31 Description: Binary data -george -- George McNinch gmcni...@gmail.com http://gmcninch.math.tufts.edu
Re: [O] Visibility cycling of plain lists?
On Mon, Dec 31, 2012 at 10:19 PM, Bastien b...@altern.org wrote: Hi James, James Harkins jamshar...@gmail.com writes: My point exactly- neither the manual nor the docstring do anything to dispel that confusion. If you do C-h v org-cycle-include-plain-lists RET you read that a value of t allows visibility cycling and that a value of 'integrate temporarily interprets list items as outline headlines. You're right; I had forgotten to expand the docstring, so I saw only the first line. The options are explained in subsequent paragraphs. The only issue left, then, is the disconnect between the value menu descriptions and the actual values. Here, I guess it would make sense to follow the Emacs convention for documenting customize-interface value menus, if there is such a convention. If not, this patch might help, adding text like this after the paragraph description: ~~ Value menu options: Never -- nil With cursor in plain list (recommended) -- t (the default) As children of outline headings -- integrate ~~ (I'm assuming the convention is not don't document.) In the org manual, it would probably be enough to add a parenthetical note: ~~ If this variable is set to 'integrate' (As children of outline headings in the customize interface), plain list items will be treated like low-level headlines. ~~ When customizing, you can either set it to Never, which is obvious. Or to `t', which is explained. I differ here -- in the menu, you don't set it to t. Or to the other value, which is the symbol 'integrate. This third value is mentioned in the docstring, and it is pretty obvious that it corresponds to As children of outline headings, as there are no other choices. Ah, I see. It's *obvious*. (I guess org-mode's target audience is smarter than I am.) I do see your point that the options are described, and I apologize for overlooking them earlier. But, if one is using the customize interface, then there remains a (small) bit of guesswork to connect the documentation to what is presented in the interface, and I think generally documentation should be there to eliminate guesswork (or at least reduce the need for it). (That's not a specific complaint to org -- on the SuperCollider mailing list, I'm constantly harping on method documentation that doesn't explain the expected types of the input and output, for the same reason -- if I have to write a short bit of test code to figure out what the method is supposed to do, then the documentation isn't complete.) hjh PS And *again* I'm bitten by the fact that I just can't get used to mailing lists where replies are sent to individual authors as well as the list address... sorry about that.
[O] patch for org-contacts to ignore radio_marks when completing
Hi, I send a patch which allows org-complete to complete if you do „J o h n TAB“ even if your contact was written as John (now you would have to type J TAB). It can be extended to remove emphasis, strongs, etc. if someone needs it. Thanks diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index 7e3cbb7..0173f1d 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -388,12 +388,17 @@ This function should be called from `gnus-article-prepare-hook'. (org-completing-read prompt (org-contacts-filter) predicate t initial-input hist def inherit-input-method)) +(defun org-contacts-format-name (name) + Format a person name to remove radio marks. + (replace-regexp-in-string org-radio-target-regexp \\1 name) + ) + (defun org-contacts-format-email (name email) Format a mail address. (unless email (error `email' cannot be nul)) (if name - (concat name email ) + (concat (org-contacts-format-name name) email ) email)) (defun org-contacts-check-mail-address (mail)
