Re: [O] How to suppress latex exporting as a list if a name that begins with a single letter
Hi Charlie, On Di, 2017-09-26 at 19:22, Charles Millar wrote: > A. Persons Name is exported as > > 1. Persons Name > > not > > A. Persons Name. What about marking as verbatim? =A. Person= Best regards Michael Strey -- http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] grab html pages and copy them into a org buffer.
Hi Uwe On Di, 2017-08-29 at 16:53, Uwe Brauer wrote: > I know about converters from html to org mode, for example pandoc, but I > remember vaguely that there are possibilities to mark a html text in > browser (firefox?) And copy it as org syntax into a buffer. > > Does anybody know about this feature or program? org-web-tools from Adam Porter https://lists.gnu.org/archive/html/emacs-orgmode/2017-07/msg00392.html Best regards Michael Strey -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] Bug: Duplicated internal crossreference IDs in org-html-publish-to-html [9.0 (release_9.0-251-gc04501 @ /usr/share/emacs/site-lisp/org/)]
On Fr, 2016-11-11 at 17:50, Nicolas Goaziou wrote: [...] >> I would expect unique IDs instead. > > Fixed. Thank you. Thank you! Best regards Michael Strey -- http://www.strey.biz * https://twitter.com/michaelstrey
[O] [PATCH] org.el: Fix bug from switch to lexical binding
Please check carefully before applying! I do not understand what I have done here but it worked for me without side effects. -- Michael Strey _ mailto:mst...@strey.biz http://www.strey.biz * https://twitter.com/michaelstrey >From b76d6ef5975e1ba0b5ad4317246e1084d43ff446 Mon Sep 17 00:00:00 2001 From: Michael Strey <mst...@strey.biz> Date: Fri, 8 Apr 2016 14:03:30 +0200 Subject: [PATCH] org.el: Fix bug from switch to lexical binding * lisp/org.el (org-check-dates-range): Fix a bug introduces with the switch to lexical binding in commit 1f49e9fdfd8b527377b5592bd65ad3be6abb9e6a. This change fixed the following bug: C-c \ D leads to error message "Symbol's value as variable is void: start-date". TINYCHANGE --- lisp/org.el | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 4f60c7f..b6d1c2d 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -17489,12 +17489,12 @@ both scheduled and deadline timestamps." (let ((case-fold-search nil) (regexp (org-re-timestamp org-ts-type)) (callback - `(lambda () + (lambda () (let ((match (match-string 1))) (and - ,(if (memq org-ts-type '(active inactive all)) - '(eq (org-element-type (org-element-context)) 'timestamp) - '(org-at-planning-p)) + (if (memq org-ts-type '(active inactive all)) + (eq (org-element-type (org-element-context)) 'timestamp) + (org-at-planning-p)) (not (time-less-p (org-time-string-to-time match) (org-time-string-to-time start-date))) -- 2.7.3
Re: [O] scheduled task without headline?
On Mo, 2016-02-22 at 21:09, hymie! wrote: > I'd really like to have my specific "note" listed in the agenda, but > what I need to do is so minor that I don't want it to have a "headline" > in my notes. Is this possible? Have you already checked the so called inline tasks? C-h f org-inlinetask-insert-task Best regards -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] Bug: Commit 2520fd654a65fe607a8ca726d7fc8fb5be07d258 breaking org-drill [8.3.3 (release_8.3.3-725-gdd15fe @ /usr/share/emacs/site-lisp/org/)]
On Di, 2016-02-02 at 22:59, Nicolas Goaziou wrote:
> Hello,
>
> Michael Strey <mst...@strey.biz> writes:
>
>> After reverting the mentioned commit, org-drill is working like expected
>> again
>> and the function call:
>>
>> (org-make-tags-matcher "")
>>
>> evaluates to:
>>
>> ("" lambda (todo tags-list level)
>> (and (member todo org-not-done-keywords) (and t t)))
>>
>> In HEAD it evaluates to:
>>
>> ("" lambda (todo tags-list level)
>> (and (member todo org-not-done-keywords) nil))
>>
> Hopefully fixed in master. Could you confirm it?
Yes, org-drill works again. Thank you!
Best regards
--
Michael Strey
http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] references to arbitrary labels in org and export to latex
On Mi, 2016-02-03 at 08:05, Christian Wittern wrote:
> I am writing a document with a lot of web references. I would like to
> bundle them at the end in the same way this is usually done with
> bibliographic references, but separately.
I would use the great org-ref package and handle the URLs like normal
bibliographic references in a biblatex .bib file with the entry type
'Online'.
Biblatex allows to have multiple bibliographies as described here:
http://texblog.org/2012/10/22/multiple-bibliographies-with-biblatex/
with
#+BEGIN_EXPORT latex
\printbibliography[title={Online references},type=online]
\printbibliography[title={Other references}, nottype=online]
#+END_EXPORT
Best regards
--
Michael Strey
http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] Bug: Commit 2520fd654a65fe607a8ca726d7fc8fb5be07d258 breaking org-drill [8.3.3 (release_8.3.3-725-gdd15fe @ /usr/share/emacs/site-lisp/org/)]
On Di, 2016-02-02 at 17:58, Nicolas Goaziou wrote:
[...]
> Could you provide an ECM?
Well, yes, maybe, but I would like to avoid this effort.
After reverting the mentioned commit, org-drill is working like expected again
and the function call:
(org-make-tags-matcher "")
evaluates to:
("" lambda (todo tags-list level)
(and (member todo org-not-done-keywords) (and t t)))
In HEAD it evaluates to:
("" lambda (todo tags-list level)
(and (member todo org-not-done-keywords) nil))
Hope that helps. If not, I will go and make my homework with the ECM.
Best regards
--
Michael Strey
http://www.strey.biz * https://twitter.com/michaelstrey
[O] Bug: Commit 2520fd654a65fe607a8ca726d7fc8fb5be07d258 breaking org-drill [8.3.3 (release_8.3.3-725-gdd15fe @ /usr/share/emacs/site-lisp/org/)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. When starting an org-drill session, I expect the answer to the question to be hidden. Since my last update, I see question and answer at the same time. I tracked the problem down to commit 2520fd654a65fe607a8ca726d7fc8fb5be07d258. In function org-drill-hide-subheadings-if the following call of org-map-entries is used: (org-map-entries (lambda () (when (and (not (outline-invisible-p)) (> (org-current-level) drill-entry-level)) (when (or (/= (org-current-level) (1+ drill-entry-level)) (funcall test)) (hide-subtree)) (push (point) drill-sections))) "" 'tree) Emacs : GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.6) of 2015-09-10 on foutrelis Package: Org-mode version 8.3.3 (release_8.3.3-725-gdd15fe @ /usr/share/emacs/site-lisp/org/) -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] Adjust Keywords
(org-align-all-tags) -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] How to enter a tag when capturing?
On Sa, 2015-12-19 at 16:48, Marcin Borkowski wrote: > I'd like to insert a tag while capturing an item. Of course, C-c C-c > finishes capture. I can insert the tag manually (and currently I'm > doing just that), but is there a better way? C-c C-q bound to org-set-tags-command. -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] Favorite contrib/ packages?
On Di, 2015-11-03 at 19:58, Kaushal Modi wrote: > What are your favorite org contrib/ packages that you simply can't > live without, and consider them to be a part of your org-mode core? org-checklist org-collector org-contacts org-dial org-download org-drill org-learn org-mime org-notmuch org-registry ox-koma-letter -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] Modification dates in Worg
On Mo, 2015-09-28 at 17:04, Ista Zahn wrote: > I've created a worg mirror on github at > https://github.com/izahn/worg-mirror/, so you can see the modification > dates via git-blame. Thank you. That will help me and maybe some other people who follow this thread. Unfortunately it does not solve the general problem. Most people access Worg via HTML. -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] convert a simple list of lines each to a orgmode header
On Mo, 2015-09-28 at 18:52, Xebar Saram wrote: > im looking for a simple way to convert a simple list of lines (i can > mark it first if needed) each to a orgmode header > anyone has such a way? Mark the region and press C-c *. -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
[O] Modification dates in Worg (was: babel header arguments tutorial?)
On Sa, 2015-09-26 at 23:39, Charles C. Berry wrote: [...] > The source is several years old and filed under the FIXME worg > directory. Both things are not visible on the page. In general there seems to be a lot of outdated stuff on Worg. It would be helpful to have at least the date of last modification on the pages. -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] Org to LaTeX export of tables
On Mo, 2015-08-24 at 01:36, Vikas Rawal wrote:
[...]
I do not want \begin{center} and \end{center}. Having those results in
some extra space between the table and the notes.
How can I get rid of it?
(setq org-latex-tables-centered nil)
Regards
--
Michael Strey
http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] Automatically encrypt on save, decrypt on open?
On Do, 2015-08-13 at 16:28, Peter Davis wrote: I'd like to store information in an org page that gets automatically encrypted when I save it, and decrypted when I open it. Is there some built-in functionality or hooks for this? Check org-crypt.el (http://orgmode.org/manual/org_002dcrypt_002eel.html) -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] Org-mode 8.3.1 bugs report
On Do, 2015-08-06, Lei Zhe wrote: [...] 2. When I call org-drill, some entries can not be shown. Only blank buffer shows up. I'm having the same problem here since about 4 weeks. It seems to occur randomly without relation to the entries. Pressing e for “edit”, moving point some lines up or down and M-x org-drill-resume is my poor workaround to proceed the drill session. Best regards -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
[O] [ANN] org-report -- Generate activity reports from Emacs Org mode
Dear list members, org-report was made as private extension to automize the generation of weekly activity reports. Maybe it's useful for others as well. Please handle with care. https://github.com/mistrey/org-report Regards -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
[O] [ANN] org-execute -- Automate recurrent jobs in Emacs Org mode
Dear list members, org-execute is a very small extension package that allows to start a named Babel code block by pressing TAB on an agenda entry. Please refer to https://github.com/mistrey/org-execute. Regards -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
[O] [ANN] org-dial
~org-dial~ --- softphone support for Emacs Org mode is published on Github now. https://github.com/mistrey/org-dial -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] sip: links
On So, 2015-06-21, Christian Thaeter wrote: [...] looks good, I'll use that instead of my hack. Look out for bugs. It's one of my very first emacs-lisp hacks. I've a minor ideas to add: Instead just append the telephone number to the end of the dial command one could use (org-replace-escapes STRING TABLE), that allows little more flexible commandline generation. Thanks for the hint. Could you please give me an example where this increased flexibility would be required? Best regards -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] sip: links
Hi Christian, On Sa, 2015-06-20, Christian Thaeter wrote: anyone of you happen to have a url handler for 'sip:' links invoking a telephony app (eg. linphone) when clicked? The attached org-dial.el provides support for a link type `tel:' as well as for dialing from properties in org-contacts. Enjoy. -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey org-dial.el Description: application/emacs-lisp
[O] Bug: sparse tree with date query fails [8.3beta (release_8.3beta-1275-gb94ef2 @ /usr/share/emacs/site-lisp/org/)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. In an org file containing timestamps I tried to create a sparse tree with C-c / D and get an error message regarding eq having only one argument. C-c / b and C-c / a show the same behaviour. The culprit seems to be this line: + '(eq (org-element-type (org-element-context) 'timestamp)) from http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=c6d9a4ec22ff59928e05debeb27139270f293526 Emacs : GNU Emacs 24.5.1 (i686-pc-linux-gnu, GTK+ Version 3.16.2) of 2015-04-20 on sammy Package: Org-mode version 8.3beta (release_8.3beta-1275-gb94ef2 @ /usr/share/emacs/site-lisp/org/) -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] [OT] A short (less than a minute), informal survey about LaTeX
Hi Marcin, On So, 2015-03-22, Marcin Borkowski wrote: [...] 1. Did you know about the savetrees package by Scott Pakin (http://www.ctan.org/pkg/savetrees)? I've heard about it but never used it. 2. Would you find it useful when producing PDF files other that scientific articles (using Org-mode or not)? Yes. I'm currently using Orgmode LaTeX export for sales activity reports, letters, Beamer presentations, minutes, and check lists. In the past I've been using LaTeX (without Orgmode) for manuals and even for data sheets. Best regards Michael -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] How do I un-spare tree a buffer?
On Mi, 2015-01-21, Tory S. Anderson wrote: [...] How do I un-sparsify my org buffer? C-c C-c -- Michael Strey http://www.strey.biz https://twitter.com/michaelstrey
Re: [O] [bug] viewing properties in column view
On Mi, 2015-01-07, Eric S Fraga wrote: On Wednesday, 7 Jan 2015 at 18:23, Michael Strey wrote: Try to write 'myproperty' in capital letters as 'MYPROPERTY'. Thanks for the suggestion. I am not sure if properties are case sensitive or not. I have always used lower case for many of my properties and things have always worked fine. In any case, I didn't get a chance to try this suggestion as Nicolas has already fixed it! Yes he has fixed my problem as well :-). But shame on me that I didn't report it. I had a very similar problem with capitalized (like ':Price:') property keys. I have not been able to reproduce it with 'emacs -Q', so there must have been an interdependence with my setup. Finally my workaround was to change my keys to all capitals. Nicolas' latest change has cured my problem as well. Thank you Nicolas! -- Michael Strey http://www.strey.biz https://twitter.com/michaelstrey
Re: [O] [bug] viewing properties in column view
Hello Eric, On Mi, 2015-01-07, Eric S Fraga wrote: [...] Can anybody point me in the right direction to get this working again? Try to write 'myproperty' in capital letters as 'MYPROPERTY'. -- Michael Strey http://www.strey.biz https://twitter.com/michaelstrey
Re: [O] org-contacts development
Hi Daimrod,
On 2014-05-29, Daimrod wrote:
Hmm, I kinda like this. It seems a bit verbose but it's better than
having multiple values per properties (IMHO).
Though, if we adopt this scheme, we would need to add some helper
bindings/functions so that we don't have to fill this by hands.
I'm using yasnippets and have snippets for organizations, job-related
contacts and private contacts.
I have attached them.
C-c C-x p helps to fill in optional properties.
I have all my contacts in one buffer with the following settings
#+BEGIN_SRC org
* Buffer settings
#+STARTUP: overview
#+STARTUP: hidestars
#+STARTUP: indent
#+TAGS: ADMIN(i) CHEF(f) EINKAUF(k) PRIVAT(t) SEKRETARIAT(s)
#+TAGS: AUTO(u) BROADCASTER(b) DAB(d) DVB(v) EMPFÄNGER(m) HOCHSCHULE(h)
NETZBETREIBER(n) SYSTEM(y) B2B B2C REG
#+TAGS: MAIL(l) PRESSE(e) KUNDE COMPETITOR
#+TAGS: ABI CI FAMILIE FREUNDE SCHULE TAICHI TURNEN
#+SEQ_TODO: TODO(t) NEXT(n) WAITING(w) | DONE(d) CANCELLED(c)
#+PROPERTY: Contact_Type_ALL individual organization
#+PROPERTY: Language_ALL de en ru
#+PROPERTY: Phone_1_Type_ALL Work Home Fax Mobile
#+PROPERTY: Phone_2_Type_ALL Work Home Fax Mobile
#+PROPERTY: Phone_3_Type_ALL Work Home Fax Mobile
#+PROPERTY: Phone_4_Type_ALL Work Home Fax Mobile
#+PROPERTY: Address_1_Type_ALL Work Home Post
#+PROPERTY: Address_2_Type_ALL Work Home Post
#+PROPERTY: Address_3_Type_ALL Work Home Post
#+PROPERTY: Website_1_Type_ALL Work Home
#+PROPERTY: Website_2_Type_ALL Work Home
#+END_SRC
Other user defined properties can be added and mapped to the appropriate
user defined keys during export.
I'm not sure to understand what you mean. Could you give more details
and maybe an example?
Actually, my statement was trivial. Orgmode allows to define and add
every kind of additional properties. What I wanted to say was that it
is possible to export those additional properties to Google Contacts as
well.
I have for instance the property :Language: that is not part of the
Google API. I use it to store the preferred language of correspondence
for my job-related contacts for mailing actions.
Google Contacts accepts such fields in the CSV file to import and
creates user defined fields from them.
Please note that org-collector tries to convert property values from
strings into numbers if possible. For postal codes with leading Zeros
this can lead to unexpected results. I did not find any other way to
solve this problem than to add a national code like in the following
example
:Address_1_Code: 01169
would lead to 1169 in the propview table.
so I replaced it with
:Address_1_Code: DE-01169
What is `org-collector' and when does it happen?
From the Orgmode manual:
An alternative way to capture and process property values into a table
is provided by Eric Schulte's org-collector.el which is a contributed
package. It provides a general API to collect properties from entries
in a certain scope, and arbitrary Lisp expressions to process these
values before inserting them into a table or a dynamic block.
I'm using org-collector to create a table that can be exported to CSV
for import into Google Contacts (and maybe other contact managers).
I've done a quick test and the 0 appears in `org-contacts-db'.
Yes, everything is fine with org-contacts. The problem comes only from
org-collector. The reason is org-collector's feature to allow Lisp
expressions to process property values. Therefore it uses the function
`org-babel-read' that detects Lisp expressions and converts strings into
numbers.
So this remark is only relevant for those who want to follow my track with the
org-collector export.
--
Michael Strey
www.strey.biz
#name : Contact Individual
#key : contact
#contributor : Michael Strey [EMAIL PROTECTED]
#expand-env: ((yas/indent-line 'fixed) (yas/wrap-around-region 'nil))
# --
${1:surname}, ${2:name}
:LOGBOOK:
- Contact added: [`(org-read-date nil nil +0d)`]
:END:
:PROPERTIES:
:Contact_Type: individual
:Organization_1_Type: company
:Organization_1_Value: ${3:organisation}
:Organization_1_Department: ${4:devision}
:Organization_1_Title: ${5:title}
:FN: $2 $1
:Given_Name: $2
:Family_Name: $1
:Nickname: $19 $1
:Address_1_Type: Work
:Address_1_Street: ${6:adr1}
:Address_1_Box: ${7:adr2}
:Address_1_Extension: ${8:adr3}
:Address_1_City: ${9:city}
:Address_1_Region: ${10:state}
:Address_1_Code: ${11:zip_code}
:Address_1_Country: ${12:country}
:Email_1_Type: Work
:Email_1_Value: ${13:company_email}
:Phone_1_Type: Work
:Phone_1_Value: ${14:tel}
:Phone_2_Type: Mobile
:Phone_2_Value: ${15:mobile}
:Phone_3_Type: Fax
:Phone_3_Value: ${16:fax}
:Website_1_Type: Work
:Website_1_Value: http://$17
:Language: $18
:END:
$0
#name : Contact Individual (private)
#key : privat
#contributor : Michael Strey [EMAIL PROTECTED]
#expand-env: ((yas/indent-line 'fixed) (yas/wrap-around-region 'nil))
# --
${1:surname}, ${2:name} :NEW:
:LOGBOOK:
- Contact added: [`(org-read-date nil nil +0d)`]
:END:
:PROPERTIES:
:Contact_Type: individual
Re: [O] org-contacts development
Reading http://orgmode.org/worg/dev/org-syntax.html#Node_Properties I just realised that my clumsy property keys are against the rules since they are containing whitespace characters. Nevertheless I still like the idea of having a Type, a number and a Value for every property that can occur multiple. Thus the properties can be easily mapped to the VCard scheme as well as to any other scheme. Thus, what I would like to propose is the following scheme: #+BEGIN_SRC org :PROPERTIES: :Contact_Type: individual or organisation :Organization_1_Type: company :Organization_1_Name: The company name :Organization_1_Department: department, business unit, division :Organization_1_Title: job title of an individual :FN: The full name :GivenName: :FamilyName: :Name_Prefix: :Name_Suffix: :Nickname: :Email_1_Type: Work :Email_1_Value: n...@company.fr :Address_1_Type: Work :Address_1_Street: The street can contain multiple lines \\ second line :Address_1_Box: Postal box :Address_1_Extension: other extensions that can occur in addresses :Address_1_City: The city :Address_1_Region: Region, federal state etc. :Address_1_Code: 12100 :Address_1_Country: France :Phone_1_Type: Work :Phone_1_Value: +33 565 623740 :Phone_2_Type: Fax :Phone_2_Value: +33 565 623070 :Website_1_Type: Work :Website_1_Value: http://www.domain.fr :Birthday: :Language: en :Salutation: :END: #+END_SRC Other user defined properties can be added and mapped to the appropriate user defined keys during export. Further remarks regarding my last e-mail: #+BEGIN: propview :id 39584cda-bff0-4b8a-9460-4fefb5b5922c :cols (Given\ Name Family\ Name ITEM Name\ Prefix Name\ Suffix Nickname EMAIL Phone\ 1\ -\ Type Phone\ 1\ -\ Value Phone\ 2\ -\ Type Phone\ 2\ -\ Value Phone\ 3\ -\ Type Phone\ 3\ -\ Value Phone\ 4\ -\ Type Phone\ 4\ -\ Value Address\ 1\ -\ Type Address\ 1\ -\ Street Address\ 1\ -\ PO\ Box Address\ 1\ -\ Extended\ Address Address\ 1\ -\ City Address\ 1\ -\ Region Address\ 1\ -\ Postal\ Code Address\ 1\ -\ Country Address\ 2\ -\ Type Address\ 2\ -\ Street Address\ 2\ -\ PO\ Box Address\ 2\ -\ Extended\ Address Address\ 2\ -\ City Address\ 2\ -\ Region Address\ 2\ -\ Postal\ Code Address\ 2\ -\ Country Address\ 3\ -\ Type Address\ 3\ -\ Street Address\ 3\ -\ PO\ Box Address\ 3\ -\ Extended\ Address Address\ 3\ -\ City Address\ 3\ -\ Region Address\ 3\ -\ Postal\ Code Address\ 3\ -\ Country Organization\ 1\ -\ Name Birthday Organization\ 1\ -\ Title Organization\ 1\ -\ Department Website\ 1\ -\ Type Website\ 1\ -\ Value LANG TAGS) :colnames (Given Name Family Name Name Name Prefix Name Suffix Nickname E-mail 1 - Value Phone 1 - Type Phone 1 - Value Phone 2 - Type Phone 2 - Value Phone 3 - Type Phone 3 - Value Phone 4 - Type Phone 4 - Value Address 1 - Type Address 1 - Street Address 1 - PO Box Address 1 - Extended Address Address 1 - City Address 1 - Region Address 1 - Postal Code Address 1 - Country Address 2 - Type Address 2 - Street Address 2 - PO Box Address 2 - Extended Address Address 2 - City Address 2 - Region Address 2 - Postal Code Address 2 - Country Address 3 - Type Address 3 - Street Address 3 - PO Box Address 3 - Extended Address Address 3 - City Address 3 - Region Address 3 - Postal Code Address 3 - Country Organization 1 - Name Birthday Oganization 1 - Title Organization 1 - Department Website 1 - Type Website 1 - Value Language org-tags) :defaultval :inherit (TAGS) :conds ((stringp KIND)) :match -ARCHIVE :noquote t Here I forgot to copy the #+END: Please note that org-collector tries to convert property values from strings into numbers if possible. For postal codes with leading Zeros this can lead to unexpected results. I did not find any other way to solve this problem than to add a national code like in the following example :Address_1_Code: 01169 would lead to 1169 in the propview table. so I replaced it with :Address_1_Code: DE-01169 -- Michael Strey mailto:mst...@strey.biz http://www.strey.biz https://twitter.com/michaelstrey
Re: [O] org-contacts development
- Region Address 1 - Postal Code Address 1 - Country Address 2 - Type Address 2 - Street Address 2 - PO Box Address 2 - Extended Address Address 2 - City Address 2 - Region Address 2 - Postal Code Address 2 - Country Address 3 - Type Address 3 - Street Address 3 - PO Box Address 3 - Extended Address Address 3 - City Address 3 - Region Address 3 - Postal Code Address 3 - Country Organization 1 - Name Birthday Oganization 1 - Title Organization 1 - Department Website 1 - Type Website 1 - Value Language org-tags) :defaultval :inherit (TAGS) :conds ((stringp KIND)) :match -ARCHIVE :noquote t #+END_SRC -- Michael Strey mailto:mst...@strey.biz http://www.strey.biz
Re: [O] setting left margin in PDF output of ORG file
On 2014-04-25, John Hendy wrote: I have to ask: is whatever was once considered the golden ratio for text-to-whitespace in printed material, or even used by Gutenberg himself for proper typesetting considered relevant/best practice today? Yes, at least partly. Verachtet mir die alten Meister nicht! (Do not condemn the old masters!) -- Richard Wagner Default Org - LaTeX article looks *ugly as all hell* to me. Check the Komascript classes. Other than theoretical principle, is there evidence that readers prefer the look of the default LaTeX article sizing? Beyond all aesthetic meanings, there are some practical aspects that are valid for all presentations of text to readers. The most important rule is that the number of characters per line shall not exceed 70. Together with the chosen font, its size, and tracking, this rule defines the width of the type area. Together with the interlinear space, this rule is relevant for the readability. The longer the line, the larger (but not to large!) the interlinear space. Thus for printed papers where the most economical use of paper is important, a multi-column layout is the way to go to get the smallest margins. -- Michael Strey www.strey.biz
Re: [O] setting left margin in PDF output of ORG file
Hi Dave, Please read http://en.wikipedia.org/wiki/Canons_of_page_construction before changing anything in the layout of margins. The typical LaTeX classes are made thorougly with those classic rules of page construction in mind. On 2014-04-23, J. David Boyd wrote: I can export an org file to a PDF no problem, looks great. However, how do I get rid of the huge left and right and top and bottom margins? I like my PDFs to have no more than .75 top, bottom, left and right. I've looked through all the latex, org-latex, org-beamer variables I can find with customize-apropos, but not having any luck. Thanks, Dave -- Michael Strey www.strey.biz
Re: [O] Patch for testing `org-open-at-point'
Hi Bastien, On 2014-04-17, Bastien wrote: The question is this: are we fine handling raw links in properties, or do we also need Org links (e.g. bracket links) there? Speaking for me, raw links is enough, and this is what I plan to implement. But maybe other users have existing use-cases for Org links there, I don't know. I have. I'm using phone links (see http://thread.gmane.org/gmane.emacs.orgmode/69406/focus=70484) in conjunction with org-contacts in the properties of my contacts. -- Michael Strey www.strey.biz
[O] [Bug] org-open-at-point does not work inside properties block
Hello, Since some days links in properties blocks do not work any more. With org-open-at-point on the URL in the following block #+begin_src org ** Media Broadcast :PROPERTIES: :KIND: organisation :URL: http://www.media-broadcast.com :END: #+end_src I get the message No link found. The same link outside the PROPERTIES block opens the browser like expected. Best regards -- Michael Strey http://www.strey.biz
Re: [O] [Bug] org-open-at-point does not work inside properties block
Hi Bastien, Thank you for your fast reply. Bastien b...@gnu.org writes: This is a temporary limitation due to the recent rewrite of `org-open-at-point'. [...] We cannot sort this out too quickly, as this needs reasonable feedback from users. I'm using links in PROPERTIES blocks on a regular basis in my contacts file. There I have email addresses, urls and phone numers that are custom links. Best regards -- Michael Strey http://www.strey.biz
Re: [O] Quotes for LaTeX export
Hi Laurens,
_...@lvh.io writes:
[...]
The preferred way to do that these days is, in the preamble:
\usepackage{csquotes}
... and then later:
\enquote{something}
I think it would make sense to support this for org, and perhaps eventually
make it default behavior. FWIW: I had no idea about this until it bit me
when my LaTeX document suddenly had bogus quotes in it.
IMHO, it would be nice to have a customizable
org-export-user-smart-quote-alist as already mentioned by Rasmus. This
would give the maximal flexibility to comply with this wish and similar wishes.
BUT in this concrete case, the problem can be tackled from the LaTeX
side as well. Section 10.8 of the documentation of the csquote package
shows a way for documents with only one language:
\documentclass{...}
\usepackage[german]{babel}
\usepackage[babel=once]{csquotes}
\defineshorthand{`}{\openautoquote}
\defineshorthand{'}{\closeautoquote}
Best regards
--
Michael Strey
http://www.strey.biz
Re: [O] LaTeX export: Unknown LaTeX class `org-article'
Peter, p...@pfdstudio.com writes: Other ideas? Did you check the availability of org-article.cls in the TeX tree using `kpsewhich org-article.cls'? Do you have an entry for org-article in org-export-latex-classes? -- Michael
Re: [O] Reading calendars in org mode: what is the best solution?
Hi Alan, alan.schm...@polytechnique.org writes: [...] I would like to have a read-only version of my calendars in my org agenda. These calendars (10 of them) currently live in Zimbra and iCould, and I am accessing them both using the native Calendar application on OS X and on my (Android) phone. I've looked at what the options are, and I can find two of them: - convert ics files into org files (http://orgmode.org/worg/org-tutorials/org-google-sync.html) I'm using the scripts from Eric S. Fraga from the above link since several months and I'm very happy with them. The only drawback that I have noticed is, that the frequent messages ~Reverting buffer `gcal-termine.org'~ are sometimes in the way in Emacs' echo area. Best regards Michael Strey -- http://www.strey.biz
Re: [O] Latex Missing number, treated as zero.
Hi Ian,
li...@wilkesley.net writes:
This is a Latex problem, but I am hoping someone here can trow some
light on it.
No, it's not a LaTeX problem.
\documentclass{scrlttr2} \usepackage[english]{babel} [NO-DEFAULT-PACKAGES]
This line is no valid LaTeX code. As you already mentioned, if you
remove `[NO-DEFAULT-PACKAGES]', the pdflatex run works.
Please check your Emacs variable org-latex-classes.
Here is what I have in this variable for my letter class:
,
| (letter_private
\\documentclass[fontsize=11pt,strey_privat]{scrlttr2}\n\\LoadLetterOption{DIN}\n[NO-DEFAULT-PACKAGES]\n[PACKAGES]\n[EXTRA]
| (\\section{%s} . \\section*{%s})
| (\\subsection{%s} . \\subsection*{%s})
| (\\subsubsection{%s} . \\subsubsection*{%s}))
`
Best regards
Michael Strey
--
http://www.strey.biz
Re: [O] [PATCH][ox-koma-letter] changed-in-buffer, subject, minor fixes
Hi Rasmus, ras...@gmx.us writes: [...] 3. When studying the KOMA manual to answer James' second question I came across the komavar title which is currently not supported. I have added support for a separate SUBJECT keyword. The heuristic is something like this (i) if title and subject are be truthful to the name no matter what, (ii) if only title or subject is said let title be subject if org-koma-letter-title-is-subject-maybe is t otherwise be truthful to name. Thank you for implementing this feature. I already missed it. [...] In 3. I would personally like to set org-koma-letter-title-is-subject-maybe to nil by defaults, but this would break backwards comparability for title keywords. I would like to encourage you to do so, even if it breaks backward compatibility. Since Koma Letter supports Title and Subject, Title should be title and Subject should be subject by default. Everything else could drive users crazy. I've been using Koma Letter for many years for various purposes. Title without subject makes sense, for instance, when writing press releases and certificates. Best regards -- Michael Strey http://www.strey.biz
[O] [OT] for German speaking readers: free LaTeX-Referenz
Forwarded from Dante mailing list: herbert.v...@fu-berlin.de writes: Hallo zusammen, auf einigen WEB-Seiten wird bereits für http://www.lehmanns.de/latex-referenz geworben. In Zusammenarbeit mit Lehmanns Media kann diese Referenz (32 Seiten) allen kostenlos zugeschickt werden. Sie steht auch zum Download auf der Seite zur Verfügung. Ein entsprechender Hinweis in anderen Newsgruppen/Mailinglisten/... ist ausdrücklich erwünscht. Diese Referenz wird der nächsten Ausgabe der TeXnischen Komödie beiliegen, sodass Mitglieder von DANTE e.V. sie automatisch erhalten. Diese wird gegen Ende November im Briefkasten liegen. Herbert -- Michael http://www.strey.biz
Re: [O] [PATCH] Table continuation strings
Hi Tom, t...@tsdye.com writes: Patch includes table continuation strings for several languages. Translations all from the internet. Caveat emptor. The German strings are fine. Best regards -- Michael Strey http://www.strey.biz
[O] Confused about org-index, org-favtable, org-reftabel, org-refer-by-number
Hello, I'm using org-reftable.el [1] from the contrib path of the Git repository since several months. It is a useful addition to integrate my personal archive of notes, data sheets, and pages that I tore out of journals into Org Mode documents. Now that I wanted to refine this system, I stumbled across the other packages mentioned in the subject. It seems that they are all revisions of the same project from Marc Ihm. IIUC, org-index.el is the newest version that was preceded by org-favtable.el, org-reftable.el, and org-refer-by-number.el. Currently we have org-favtable.el and org-reftable.el in the contrib path whilst org-index.el is only available via Worg [2]. Marc, could you please clarify this confusion? Anyway, thank you for sharing this add-on! Best regards Michael Strey Footnotes: [1] http://orgmode.org/worg/code/elisp/org-reftable.el [2] http://orgmode.org/worg/code/elisp/org-index.el -- Michael Strey http://www.strey.biz
Re: [O] [html] non-lists showing up as lists
Bastien b...@gnu.org writes: 4. Define that lists alway have to have a newline in front of them. I presume Michael means blank line. I like this. Mhhh... I don't. Yes, I meant blank lines and after rethinking I don't like it either. My reason for not liking them is the LaTeX exporter. The current exporter respects the difference between the following two examples. #+begin_src org-mode Here is a line of text directly followed by a list - item - item #+end_src #+begin_src org-mode Here is a line of text followed by a blank line followed by a list - item - item #+end_src The blank line makes a difference in LaTeX's PDF output. Michael -- mailto:mst...@strey.biz http://www.strey.biz
Re: [O] [html] non-lists showing up as lists
Hi everyone, Just for completeness Carsten Dominik carsten.domi...@gmail.com writes: [...] Possibilities: 1. We could change the parser to ignore lists where the first item does not start with `1.' or `a)'. But this would be a pretty serious change. 2. We could implement a good function that could find problematic cases, so that they can be fixed by hand. This is basically what Nick proposed - only it would be implemented in Lisp. 3. We could implement a function that finds and fixes such issues. It would basically scan the buffer and find lists that have only a single item, not starting with 1, and change the wrapping to fix it. 4. Define that lists alway have to have a newline in front of them. 5. Define that lists always have to be indented. My favourite would be 4. Michael Strey -- mailto:mst...@strey.biz http://www.strey.biz
Re: [O] [Patch] phone links...
Daimrod daim...@gmail.com writes: While merging a patch (from Feng Shu) I have found a bug in `org-contacts-split-property'. Though the docstring says that OMIT-NULLS is forced to t when SEPARATORS is nil (just like `split-string'), it wasn't the case. I've pushed a fix; could you check on your side that it doesn't break anything in your workflow? I'm fine with your update. Thank you for the correction! -- Michael Strey mailto:mst...@strey.biz http://www.strey.biz
Re: [O] Trigger org-capture window using linux shortcut key
Hi Jackin, On Wed, May 22, 2013 at 06:40:39AM +, Jackin wrote: I am wondering if it is possible to start a org-capture window (when not within emacs) using a shortcut key. Org-protocol allows this to be done from a web browser or adobe reader which is very useful. But I am thinking of a more general solution, for triggering a org-capture window from any where in Linux - type in something and - C-c c-c. Any ideas or solutions? Thanks in advance. I've implemented this behaviour for my Xmonad desktop. The solution consists of two parts 1. The configuration of a shortcut calling a shell script in the Xmonad configuration file .xmonad/xmonad.hs 2. A shell script simulating the keystrokes to change to the virtual desktop were my Emacs lives and calling org-capture. #+BEGIN_SRC shell #!/bin/sh xdotool key Super+m 7 emacsclient -e '(org-capture)' #xdotool key Super+0 #+END_SRC -- Michael Strey www.strey.biz
Re: [O] [Patch] phone links...
Greg,
Here are the reworked patches.
0390: fixes two typos
0391: contains all the changes from my last patch and your corrections
0392: introduces a constant for the default value of separators
Best regards
Michael Strey
On Sat, Apr 20, 2013 at 05:59:39PM +0200, Daimrod wrote:
Michael Strey mst...@strey.biz writes:
Oh =:-|, another struggle with Git. I'm still learning and will do my best.
If you're not already using magit[1] I highly recommend it to you. You
can use it to commit only a portion of the changes (you can also do it
with git commit --interactive but I find it easier with magit).
Thanks for the hint. It helped a lot.
--
Michael Strey
www.strey.biz
From 2b59a2800de7066dde72121bc72ba75ea88f3c5a Mon Sep 17 00:00:00 2001
From: Michael Strey mst...@strey.biz
Date: Fri, 26 Apr 2013 12:06:34 +0200
Subject: [PATCH 390/392] org-contacts: Fix two typos in comments
* contrib/lisp/org-contacts.el (org-contacts-db): fix typo in the
word `matching'.
* contrib/lisp/org-contacts.el (org-contacts-complete-group): fix typo
in the word `found'.
TINYCHANGE
---
contrib/lisp/org-contacts.el | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el
index a3c4aed..626ad7a 100644
--- a/contrib/lisp/org-contacts.el
+++ b/contrib/lisp/org-contacts.el
@@ -225,7 +225,7 @@ This overrides `org-email-link-description-format' if set.
org-contacts-db))
(defun org-contacts-filter (optional name-match tags-match)
- Search for a contact maching NAME-MATCH and TAGS-MATCH.
+ Search for a contact matching NAME-MATCH and TAGS-MATCH.
If both match values are nil, return all contacts.
(if (and (null name-match)
(null tags-match))
@@ -433,7 +433,7 @@ A group FOO is composed of contacts with the tag FOO.
(or (cdr (assoc-string ALLTAGS (caddr
contact))) ) :)))
(list start end
(if (= (length completion-list) 1)
- ;; We've foudn the correct group, returns the address
+ ;; We've found the correct group, returns the address
(lexical-let ((tag (get-text-property 0 'org-contacts-group
(car completion-list
(lambda (string pred optional to-ignore)
--
1.8.2
From 68145d055b7a48821d9aec308cd44764a5b889ec Mon Sep 17 00:00:00 2001
From: Michael Strey mst...@strey.biz
Date: Fri, 26 Apr 2013 12:29:55 +0200
Subject: [PATCH 391/392] Org-contacts: Allow org links in properties
* contrib/lisp/org-contacts.el (org-contacts-split-property):
Introduce a custom version of split-string that keeps org links
intact.
* contrib/lisp/org-contacts.el (org-contacts-strip-link): Introduce a
new function that removes brackets, description, link type and colon
from an org link string returning the pure link target.
* contrib/lisp/org-contacts.el (provide 'org-contacts): Remove a
redundant line.
* contrib/lisp/org-contacts.el (org-contacts-complete-group,
org-contacts-complete-name, org-contacts-view-send-email,
org-contacts-get-icon, org-contacts-vcard-format): Apply the new
functions to the already existing functions extracting telephone
numbers and email addresses from the properties.
Allowed separators for email addresses and phone numbers are `,', `;'
and whitespace. `:' is not allowed anymore as separator to avoid
confusion with implizit links.
Examples of properties that are possible after those changes:
* Surname, Name
:PROPERTIES:
:EMAIL:mailto:te...@test.de; [[mailto:n...@test.de]] f...@bar.biz
:PHONE:[[tel:+49 351 4129535]], +491766626196 [[+49 (351) 41295-35]]
:END:
Phone links of the form [[tel:+49 351 412 95-35][My phone number]] or
[[tel:+49 351 41295-35]] are expected. `-', `/', `(', `)' and
whitespace characters are allowed in telephone numbers.
---
contrib/lisp/org-contacts.el | 73
1 file changed, 61 insertions(+), 12 deletions(-)
diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el
index 626ad7a..eb3fc09 100644
--- a/contrib/lisp/org-contacts.el
+++ b/contrib/lisp/org-contacts.el
@@ -445,11 +445,11 @@ A group FOO is composed of contacts with the tag FOO.
;; returned by `org-contacts-filter'.
for contact-name = (car contact)
;; Grab the first email of the contact
- for email = (car (split-string
+ for email = (org-contacts-strip-link
(car (org-contacts-split-property
(or
(cdr (assoc-string
org-contacts-email-property
(caddr contact
Re: [O] phone links...
Hi Greg, Thank you for looking into my debut feature! On Wed, Apr 17, 2013 at 12:22:14AM +0200, Daimrod wrote: Michael Strey mst...@strey.biz writes: [...] It allows entries like in the following example without effecting org-contacts current functions. #+BEGIN_SRC org * Surname, Name :PROPERTIES: :EMAIL:mailto:te...@test.de; [[mailto:n...@test.de]] f...@bar.biz :PHONE:[[tel:+49 351 4129535]], +491766626196 [[+49 (351) 41295-35]] ^ should be :PHONE:[[tel:+49 351 4129535]], +491766626196 [[tel:+49 (351) 41295-35]] :END: #+END_SRC [...] Thank you for your patch, though here are a few suggestions: - It looks like `chomp' does the same thing the `org-trim' (in `org.el') if so you should use it. Done. Thanks for the hint. - You should use `org-link-display-format' instead of `org-contacts-strip-link'. I don't think so. `org-link-display-format' returns the description of the link if there is one. My `org-contacts-strip-link' always returns the target. Using `org-link-display-format' would lead to wrong results with links like [[mailto:f...@bar.com][foo (at) bar (dot) com]] [[tel:+49 351 4129535][+49 (0)351 4129535]] - You have done some unrelated changes (fix some typos, ...), could you provide a separated patches for them? Oh =:-|, another struggle with Git. I'm still learning and will do my best. Regarding `org-contacts-split-property', I haven't found anything about multiple values within a node property in `org-element' and the syntax description doesn't mention it, so you were right to roll your own. :) That wasn't me. This (disputable) feature was already there for the :EMAIL: proprerty. Actually, I don't like multiple values within a node property and would prefer a VCard-like syntax like #+BEGIN_SRC org *** Strey, Michael :PROPERTIES: :KIND: individual :ORG: STREY Consult :FN: Michael Strey :N:Strey;Michael;; :ADR;TYPE=home:;;my street;my city;federal state;post code;my country :EMAIL: mailto:st...@myprovider.de :EMAIL;PREF=1:mailto:m...@mycompany.biz :TEL;TYPE=fax,work:[[tel:0321 21104568]] :TEL;TYPE=fax,home:[[tel:0351 4129535]] :TEL;TYPE=voice,home:[[tel:0351 4129535]] :LANG: de :ICON: ~/GTD/Icons/icon-strey_michael.jpg :END: #+END_SRC However, I think it would be better to store the separators in a variable (like `org-contacts-property-values-separator') and maybe even to use it by default instead of `split-string-default-separators' because we use it more and because it's easy to forget. That was already hard-coded before in Feng's `org-contacts-vcard-format'. But yes, you are right. Since it is limited by some constraints we should make it an extra variable. +(loop for email in (org-contacts-split-property email-list) + for gravatar = (gravatar-retrieve-synchronously (org-contacts-strip-link email)) This should be correctly and worked for me during my tests. Confusingly `email-list' is not a list but a string here. Regards -- Michael Strey http://www.strey.biz
Re: [O] phone links...
On Tue, Apr 09, 2013 at 09:31:40AM +0200, Michael Strey wrote:
[...]
The problem is on the side of org-contacts. Org-contacts does not
support links in its properties.
[...]
This shortcoming effects not only the phone links but email links as
well.
Attached is a patch to allow org links in org-contacts properties.
It allows entries like in the following example without effecting
org-contacts current functions.
#+BEGIN_SRC org
* Surname, Name
:PROPERTIES:
:EMAIL:mailto:te...@test.de; [[mailto:n...@test.de]] f...@bar.biz
:PHONE:[[tel:+49 351 4129535]], +491766626196 [[+49 (351) 41295-35]]
:END:
#+END_SRC
Phone links of the form [[tel:+49 351 412 95-35][My phone number]] or
[[tel:+49 351 41295-35]] are expected. `-', `/', `(', `)' and
whitespace characters are allowed in telephone numbers.
--
Michael Strey
www.strey.biz
From 69ae791cd552bacdcbc99af99a82ab699fa16d36 Mon Sep 17 00:00:00 2001
From: Michael Strey mst...@strey.biz
Date: Fri, 12 Apr 2013 12:33:16 +0200
Subject: [PATCH 174/174] Org-contacts: Allow org links in properties
* org-contacts.el (org-contacts-split-property, chomp): Introduce a custom
version of split-string that keeps org links intact. `chomp' is a
helper function for `org-contacts-split-property'.
* org-contacts.el (org-contacts-strip-link): Introduce a new function
that removes brackets, description, link type and colon from an org
link string returning the pure link key.
* org-contacts.el (org-contacts-complete-group)
(org-contacts-complete-name, org-contacts-view-send-email)
(org-contacts-get-icon, org-contacts-vcard-format): Apply the
new functions to the already existing functions extracting telephone numbers
and email addresses from the properties.
Allowed separators for email addresses and phone numbers are `,', `;'
and whitespace. `:' is not allowed anymore as separator to avoid
confusion with implizit links.
Examples of properties that are possible after those changes:
* Surname, Name
:PROPERTIES:
:EMAIL:mailto:te...@test.de; [[mailto:n...@test.de]] f...@bar.biz
:PHONE:[[tel:+49 351 4129535]], +491766626196 [[+49 (351) 41295-35]]
:END:
Phone links of the form [[tel:+49 351 412 95-35][My phone number]] or
[[tel:+49 351 41295-35]] are expected. `-', `/', `(', `)' and
whitespace characters are allowed in telephone numbers.
---
contrib/lisp/org-contacts.el | 83
5 files changed, 106 insertions(+), 28 deletions(-)
diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el
index 65eeea8..a502674 100644
--- a/contrib/lisp/org-contacts.el
+++ b/contrib/lisp/org-contacts.el
@@ -218,7 +218,7 @@ This overrides `org-email-link-description-format' if set.
org-contacts-db))
(defun org-contacts-filter (optional name-match tags-match)
- Search for a contact maching NAME-MATCH and TAGS-MATCH.
+ Search for a contact matching NAME-MATCH and TAGS-MATCH.
If both match values are nil, return all contacts.
(if (and (null name-match)
(null tags-match))
@@ -426,7 +426,7 @@ A group FOO is composed of contacts with the tag FOO.
(or (cdr (assoc-string ALLTAGS (caddr
contact))) ) :)))
(list start end
(if (= (length completion-list) 1)
- ;; We've foudn the correct group, returns the address
+ ;; We've found the correct group, returns the address
(lexical-let ((tag (get-text-property 0 'org-contacts-group
(car completion-list
(lambda (string pred optional to-ignore)
@@ -438,11 +438,11 @@ A group FOO is composed of contacts with the tag FOO.
;; returned by `org-contacts-filter'.
for contact-name = (car contact)
;; Grab the first email of the contact
- for email = (car (split-string
+ for email = (org-contacts-strip-link
(car (org-contacts-split-property
(or
(cdr (assoc-string
org-contacts-email-property
(caddr contact)))
- )))
+
;; If the user has an email address,
append USER EMAIL.
if email collect
(org-contacts-format-email contact-name email))
, )))
@@ -459,14 +459,14 @@ A group FOO is composed of contacts with the tag FOO.
;; returned by `org-contacts-filter'.
for contact-name = (car contact)
;; Build the list
[O] evil-mode movement keys in the agenda?
Marcelo, I'm using only the following two lines. #+BEGIN_SRC emacs-lisp ;;; org agenda -- leave in emacs mode but add j k (define-key org-agenda-mode-map j 'evil-next-line) (define-key org-agenda-mode-map k 'evil-previous-line) #+END_SRC It's a good compromise. Regards -- Michael Strey http://www.strey.biz
Re: [O] phone links...
Here is the most important part of Mat's reply: , | note that tel: is a common uri for indicating that something is a | telephone number (http://tools.ietf.org/html/rfc3966) ` Seems that we should prefer 'tel' as key for the phone link. Regards -- Michael Strey www.strey.biz
Re: [O] phone links...
FYI, I just posted the following mail to the MobileOrg mailing list. , | Hello, | | I'm using a contact data base inspired by org-contacts, where contact | details are stored in the properties drawer. | | First question: Are there any plans to show drawer content in the MobileOrg | read view (not only in the edit view)? | | The contact details contain phone numbers as well. Recently we had some | discussion about phone links in the Org-Mode mailing list. This inspired | me to make a little test with various forms of links and phone numbers. | | I synchronised the following contact with MobileOrg. | | #+BEGIN_SRC org | ** Surname, Name | :PROPERTIES: | :EMAIL:te...@test.de; n...@test.de | :PHONE:+493514129535; +491766626196 | :END: | | Visible as link and working: | [[tel:+493514129535][+49 (0)351 41295-35]] | [[tel:+49 (351) 41295-35][+49 (0)351 41295-35]] | | Visible as link but not working: | [[phone:+493514129535][+49 (0)351 41295-35]] | | Not recognized as links by MobileOrg: | [[tel:+49 351 4129535]] | [[tel:+493514129535]] | [[phone:+49 351 4129535]] | [[phone:+49 (351) 4129535]] | [[phone:+493514129535]] | | Not working: | +493514129535 | +49 351 4129535 | +49 351 41295-35 | +49 (351) 4129535 | #+END_SRC | | In MobileOrg some of the above links are displayed as links and some not. | The links with the key tel: lead me to the phone application on my | smartphone, those with the key phone don't. Pure numbers sometimes lead | to the phone app but only parts of the complete number are transmitted. | | What is the reason for the tel: links working and the phone: links not? | AFAIK non of them is supported yet by Org-Mode. ` -- Michael Strey www.strey.biz
Re: [O] phone links...
Robert, On Mo, Apr 08, 2013 at 09:44:12 -0500, Robert Goldman wrote: Michael Strey wrote: Currently org-phone.el as well as my org-dial.el are incompatible with org-contacts. The only idea behind my proposal was to make the contributors of both packages aware of each other. Can you explain what makes org-phone incompatible with org-contacts? Maybe my naming of some function? The problem is on the side of org-contacts. Org-contacts does not support links in its properties. Thus, currently the only solution to use the advantages of org-contacts and org-phone is to give the information twice, like in the following example. #+BEGIN_SRC org * Strey, Michael :PROPERTIES: :EMAIL:mst...@strey.biz f...@bar.com :PHONE:+493514129535 +491263213 :END: [[mailto:mst...@strey.biz]] [[mailto:f...@bar.com]] [[phone:+49 (0)351 41295-35]] [[phone:+49 126 3213]] #+END_SRC This shortcoming effects not only the phone links but email links as well. Regards -- Michael Strey www.strey.biz
Re: [O] phone links...
On Tue, Apr 09, 2013 at 07:19:35AM -0500, Robert Goldman wrote: [...] Again, I am not an org-contacts user, so this may be a stupid question, but how does org-contacts know when it has a contact? I am looking at the sample record you present above, and it looks just like an org-mode header to me. The original idea behind org-contacts was to treat every heading containing the property :EMAIL: as contact. This has been extended to a set of customisable properties that define a heading as contact. By default :EMAIL:, :PHONE:, :ADDRESS:, or :BIRTHDAY: make a contact from any normal heading. Best regards -- Michael Strey www.strey.biz
Re: [O] phone links...
Robert, On Do, Apr 04, 2013 at 09:38:48 -0500, Robert P. Goldman wrote: [...] I will be happy to include this into contrib (and do the relevant assignment) at any time when people think that it is sufficiently ready to go. I have been testing it in contrib/ in a testing branch in my git repo. What about integrating these few functions into org-contacts? Most users will use telephony functions in conjunction with a contact database. The recently applied patches from Feng are already steps into this direction. The next logical step would be to define some basic rules about how to write phone numbers and to support links in the EMAIL and PHONE properties like in the following example. #+BEGIN_SRC org * Surname, Name :PROPERTIES: :EMAIL:mailto:f...@bar.com :PHONE:[[phone:+49 351 4129535]]; [[phone:+49 176 6626196]] :END: #+END_SRC Moreover the definition of the phone link would allow to extend the current functionality of MobileOrg by a phone call function. Regards -- Michael Strey www.strey.biz
Re: [O] phone links...
On Mo, Apr 08, 2013 at 07:47:52 -0500, Robert Goldman wrote: Michael Strey wrote: [...] What about integrating these few functions into org-contacts? I am very reluctant to do this. I don't use org-contacts at all, but I *do* like to have phone numbers in my TODO items. Actually, I do not use org-contacts either but I use an org file as contact data base that follows the conventions defined in org-contacts. Nevertheless, I would like to be able to use some of the newer functions of org-contacts, namely the VCard export. Currently org-phone.el as well as my org-dial.el are incompatible with org-contacts. The only idea behind my proposal was to make the contributors of both packages aware of each other. I think we can get an appropriate combination by having org-phone be free-standing, and simply let the org-contacts user adopt them if s/he likes. Yes, of course, with some persuading. Related question: if the org-contact entries are *known* to be phone numbers (keyed by the field), why not automagically treat those values as phone numbers, instead of requiring them to be phone links (which add cruft to the files)? And similarly for EMAIL. I.e., why not simply have: #+BEGIN_SRC org * Surname, Name :PROPERTIES: :EMAIL:f...@bar.com :PHONE:+49 351 4129535; +49 176 6626196 :END: #+END_SRC ? That would be convenient indeed. But considering the given syntax rules for links in org-mode, I'm not sure whether I really would like it. Too much magic can be confusing. Moreover that would create a dependency between org-contacts and org-phone. Org-contacts would require org-phone in order to work as intended, thus creating a strong argument for my proposal of merging both packages. Regards -- Michael Strey www.strey.biz
Re: [O] phone links...
Hi Robert, On Wed, Apr 03, 2013 at 10:05:57AM -0500, Robert Goldman wrote: On 4/3/13 Apr 3 -9:52 AM, Michael Strey wrote: This gives me the opportunitie to publish my own attempt to implement telephone functionality into org. I'm using Linphone (http://www.linphone.org/) instead of Skype. Thanks! I am folding the linphone code in to make org-phone more generic. Great! Question: why the removal of (0)? For international calls? Why (0) only, instead of any 0 prefix? Also, do you ever want to remove it anywhere but as a prefix? If so, maybe DELETE is the wrong function call. Linphone requires the numbers in form 0033456833 or +33456833 respectively. Usually my phone links look like [[tel:+49 351 4129535]]; but since I imported data sets from a larger contact data base that had evolved over time, I ended up with stuff like this in my data base: 1. [[tel:0033 (0) 4568-33]] 2. [[tel:+49 (0)3 8899 66]] 3. [[tel:0351 41295-35]] 4. [[tel:0351/4129535]] 5. [[tel:(0351) 412 95-35]] My filter function currently handles the cases 1. to 4. but (for no other reason than carelessness) not 5. #+BEGIN_SRC emacs-lisp (defun trim-phone-number (phonenumber) Remove whitespaces from a telephone number (setq trimmed_phonenumber (mapconcat 'identity (delete (0) (split-string phonenumber [ /-])) ))) #+END_SRC Regards -- Michael Strey www.strey.biz
Re: [O] phone links...
On Thu, Apr 04, 2013 at 10:26:53AM +0200, Michael Strey wrote: [...] Usually my phone links look like [[tel:+49 351 4129535]]; but since I imported data sets from a larger contact data base that had evolved over time, I ended up with stuff like this in my data base: 1. [[tel:0033 (0) 4568-33]] 2. [[tel:+49 (0)3 8899 66]] 3. [[tel:0351 41295-35]] 4. [[tel:0351/4129535]] 5. [[tel:(0351) 412 95-35]] My filter function currently handles the cases 1. to 4. but (for no other reason than carelessness) not 5. [...] Here is a re-work of the filter function that handles all off the above cases correctly. #+BEGIN_SRC emacs-lisp (defun trim-phone-number (phonenumber) Remove whitespaces from a telephone number (setq trimmed_phonenumber (mapconcat 'identity (split-string (mapconcat 'identity (split-string phonenumber (0)) ) [()/ -]) ))) #+END_SRC I'm a Elisp newbie. I'm sure that there are smarter solutions to solve this problem. Regards -- Michael Strey www.strey.biz
Re: [O] phone links...
This gives me the opportunitie to publish my own attempt to implement telephone functionality into org. I'm using Linphone (http://www.linphone.org/) instead of Skype. Best regards -- Michael Strey www.strey.biz ;;; org-dial.el --- Provide org links to dial with the softphone ;;; application linphone ;; Copyright (C) 2011 Michael Strey ;; Author: Michael Strey mst...@strey.de ;; Keywords: dial, phone, softphone, contacts, hypermedia ;; This program is free software; you can redistribute it and/or modify ;; it under the terms of the GNU General Public License as published by ;; the Free Software Foundation, either version 3 of the License, or ;; (at your option) any later version. ;; This program is distaributed in the hope that it will be useful, ;; but WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;; GNU General Public License for more details. ;; You should have received a copy of the GNU General Public License ;; along with this program. If not, see http://www.gnu.org/licenses/. ;;; Commentary: ;; `org-dial.el' defines the new link type `dial' for telephone ;; numbers in contacts (refer to org-contacts). Calling this link type ;; leads to the execution of a linphone command dialing this number. ;;; Code: (require 'org) ;; org link functions ;; dial link (org-add-link-type tel 'org-dial) (defcustom org-dial-program linphonecsh dial Name of the softphone executable used to dial a phone number in a `tel:' link. :type '(string) :group 'org) (defun org-dial (phonenumber) Dial the phone number. The variable phonenumber should contain only numbers, whitespaces, backslash and maybe a `+' at the beginning. ;; remove whitespaces from phonenumber (shell-command (concat org-dial-program (trim-phone-number phonenumber (defun trim-phone-number (phonenumber) Remove whitespaces from a telephone number (setq trimmed_phonenumber (mapconcat 'identity (delete (0) (split-string phonenumber [ /-])) ))) (provide 'org-dial) ;;; org-dial.el ends here
Re: [O] Active timestamp drawer with inactive creation-date
On Wed, Mar 13, 2013 at 10:04:52AM +0100, Bastien wrote: [...] I think you want this: (setq org-expiry-inactive-timestamps t) Thank you for the hint to org-expiry, Bastien. Maybe this link is helpful as well: http://stackoverflow.com/questions/12262220/add-created-date-property-to-todos-in-org-mode -- Michael Strey www.strey.biz
Re: [O] Active timestamp drawer with inactive creation-date
Hi Alex, On Tue, Mar 12, 2013 at 01:56:06PM +0100, Alexander Poslavsky wrote: I actively use timestamps to plan my day. When I have a task, I add a time-stamp to it with C-. Then I plan the task, for example, for tomorrow. I end up with: ** important task 2013-03-13 Wed :PROPERTIES: :CREATED: 2013-03-12 Tue 13:52 :END: How do you create the :CREATED: property with the active timestamp? Regards -- Michael Strey www.strey.biz
Re: [O] Org-mode latex pdf export issue: Underlined lines not breaking properly
Hi Sanjib, This is a known LaTeX issue that has nothing to do with Org. Please check the LaTeX packages ulem.sty and soul.sty or simply don't use underlining -- it's anyway ugly. Best regards -- Michael Strey www.strey.biz
Re: [O] [patch] ox-koma-letter
Hello,
On Mon, Mar 04, 2013 at 09:38:38PM +0100, Nicolas Goaziou wrote:
[...]
Headlines are also possible, with a :location: property, which could be
set to, e.g. closing. See also:
http://orgmode.org/worg/org-tutorials/org-e-groff-documentation.html
for a syntax based on headlines.
Here is a draft proposal for a user interface using Nicola's suggestion:
#+BEGIN_SRC org
#+LATEX_CLASS: letter
#+LCO: strey_consult, DINmtext, sections
#+LANGUAGE: en
#+AUTHOR: Michael Strey
#+EMAIL: mst...@strey.biz
#+DATE: \today
#+TITLE: KomaScript Allows Title and Subject
#+SUBJECT: User interface of org-koma-letter.el
#+SPECIALMAIL: by registered mail
#+TO_ADDRESS: Name\\Street\\Postcode City
#+YOURREF: LT/21/20
#+YOURMAIL: 20.09.2012
#+MYREF: St/foo/bar
#+CUSTOMER: customer name
#+INVOICE: invoice no.
#+OPENING: Dear Org-Mode user,\\dear developers,
#+CLOSING: Regards,
#+AFTER_LETTER: here is code to go after \end{letter}, e.g. for pdfpages
inclusion
* About this document :BODY:
This is an example of a letter that contains all options allowed in
Koma-Script letters. It shall illustrate the proposed user interface
of ox-koma-letter.el for further discussion.
I used properties for all information having a fixed place in the
letter layout and headlines with tags for those parts of the content of
of the letter that have to be typeset in a distinct order.
* Sectioning in Letters :BODY:
With the letter class option =sections.lco= KomaScript supports
sectioning in the body of a letter. Advocates like this feature.
* Enclosures:ENCL:
a first attachment\\a second one
* Copies go to:CC:
Worg\\Org-Mode mailing list
* PS :PS:
PS: Usually a postsriptum is a short trailer but for those who like
to write more, it should allow multiple paragraphs.
Here is one.
#+END_SRC
Regards,
--
Michael Strey
www.strey.biz
Re: [O] [patch] ox-koma-letter
On Tue, Mar 05, 2013 at 01:23:40PM +0100, Rasmus wrote:
[...]
What happens to headlines without a tag? Would they be
read as part of the body or would untagged headliens just be ignored?
Untagged sections shall be treated as body.
Updated proposal:
#+BEGIN_SRC org
#+LATEX_CLASS: letter
#+LCO: strey_consult, DINmtext, sections
#+LANGUAGE: en
#+AUTHOR: Michael Strey
#+EMAIL: mst...@strey.biz
#+DATE: \today
#+TITLE: KomaScript Allows Title and Subject
#+SUBJECT: User interface of org-koma-letter.el
#+SPECIALMAIL: by registered mail
#+TO_ADDRESS: Name\\Street\\Postcode City
#+YOURREF: LT/21/20
#+YOURMAIL: 20.09.2012
#+MYREF: St/foo/bar
#+CUSTOMER: customer name
#+INVOICE: invoice no.
#+OPENING: Dear Org-Mode user,\\dear developers,
#+CLOSING: Regards,
#+AFTER_LETTER: here is code to go after \end{letter}, e.g. for pdfpages
inclusion
* About this document :BODY:
This is an example of a letter that contains all options allowed in
Koma-Script letters. It shall illustrate the proposed user interface
of ox-koma-letter.el for further discussion.
I used properties for all information having a fixed place in the
letter layout and headlines with tags for those parts of the content of
of the letter that have to be typeset in a distinct order.
* Sectioning in letters :BODY:
With the letter class option =sections.lco= KomaScript supports
sectioning in the body of a letter. Advocates like this feature.
If =sections.lco= was not loaded, headlines shall be ignored.
* Sections without tags
Sections without tags should be read as if they had the tag =:BODY:=.
* Enclosures:ENCL:
a first attachment\\a second one
* Copies go to:CC:
Worg\\Org-Mode mailing list
* PS :PS:
PS: Usually a postsriptum is a short trailer but for those who like
to write more, it should allow multiple paragraphs.
Here is one.
#+END_SRC
--
Michael Strey
www.strey.biz
Re: [O] [patch] ox-koma-letter
Hi Alan, On Mon, Mar 04, 2013 at 08:19:58AM +0100, Alan Schmitt wrote: [...] So I guess the only part of the letter design I'm worried about is having a 'ps' with several paragraphs. The option below makes an opening with two paragraphs. #+BEGIN_SRC org #+OPENING: Sehr geehrter Herr Meier,\\liebe Frau Schulze, #+END_SRC So where is the problem with PS? BTW: Do you use PS in printed letters? Regards, -- Michael Strey www.strey.biz
Re: [O] [patch] ox-koma-letter
Rasmus, On Wed, Feb 27, 2013 at 01:13:25PM +0100, Rasmus wrote: [...] In fact to use the scrlttr2 support in Org I had to adjust a LCO files because it's currently loaded after LATEX_HEADER arguments (so all customization was overwritten). I didn't like that. After this remark I checked my changes and compared them with the default code and behaviour of ox-koma-letter with the result that I reverted all of my deletions. The mentioned feature provides just the right hierarchy for my use case. - LCO overrides everything - options in the file override options in customization - options in customization override defaults in ox-koma-letter Nevertheless I agree that the nil check solution would allow more flexibility. [...] Maybe we should write a user guide *before* further implementation steps. I agree. A question zero is whether we eventually want to have an org-letter which could, in principle, output to something different than scrlttr2. IMO one *good* solution for writing letters is enough. scrlttr2 is perfect for me and covers at least European conventions about how letters should look like. I don't know which LaTeX classes people from other parts of the globe prefer. At least we should try to make the user interface (the list of variables) universal enough to cover other classes as well. Other things: - Cleaning defaults - Only insert KOMAVARs when non-nil. - Which variables to include. E.g. Michael's list vs. every komavar. - consider the order of KOMAVARs, e.g. do we really want LATEX_HEADER before LCO-like stuff? Do we want a KOMA_HEADER (or LETTER_HEADER) which comes after LCO? What to you think? Good plan. I will provide you with the last version of my modification by PM and write a How To. Best regards -- Michael Strey www.strey.biz
Re: [O] [patch] ox-koma-letter
On Tue, Feb 26, 2013 at 10:14:28PM +0100, Rasmus wrote:
[...]
Wouldn't it be better to use Markus Kohm's concept of letter class
options to set all the static stuff?
Potentially. What do you mean by letter class options? Are you
referring to customized LCO files or do you refer to e.g. customized
org-latex-classes?
I mean customized LCO files. For my former company I had made a letter
class for business letters based on scrlttr2.cls with two LCO files.
the first LCO file *company.lco* contained the general information about
the company (address, bank account, etc.). A second LCO file
*my_name.lco* contained the personal information of (e-mail address,
name, phone extension). With *my_name.lco* calling *company.lco* the
document class command for my letter finally was:
\documentclass[my_name]{our_company_letter_class}
With suitable setting of org-latex-classes not even the LCO feature
would be needed in ox-koma-letter. However I would leave it there for
more flexibility.
[...]
Even when using a dedicated LCO files and or org-latex-classes it
might be appropriate to overwrite variables.
Yes, I can imagine such cases. My problem with the current
implementation was, that for instance, the phone number was preset in
org-latex-classes. That urged me to customize this variable although
everything was already well defined in *my_name.lco*. So, please take
care to preset such variables with nil, where nil shall have the meaning
of 'ignore this variable'.
In any case I don't have a strong opinion on this issue and your
approach also makes sense.
Maybe we should write a user guide *before* further implementation steps.
2. Added AFTER_CLOSING and AFTER_LETTER keywords for arbitrary code
after \closing{.} and \end{letter}, respectively.
[...]
b. Would it be better to have a dedicated, say, PS and ENCL rather
than the generic AFTER_CLOSING?
I would opt for dedicated variables.
Fine by be.. At the very least these should come in the order that
they are specified in the document, I guess. E.g. I should be able to
place ENCL before PS in the output, if I so desire.
Mmmh ... never thought about this aspect. I simply dictated the order
of CC, ENCL and PS in my implementation. Thus your current
AFTER_CLOSING is the best solution, if you want to provide full
flexibility.
For arbitrary code I find AFTER_CLOSING and AFTER_LETTER nice.
E.g. for pdfpages inclusions.
Agreed.
Best regards
--
Michael Strey
www.strey.biz
Re: [O] [BUG, LaTeX] LATEX_CLASS_OPTIONS don't always work
Hi Nicolas, On Wed, Feb 20, 2013 at 08:27:31PM +0100, Nicolas Goaziou wrote: [...] Thank you for the detailed report. It should be fixed. I confirm, it works. Thank you! And thanks as well for the lesson in regular expressions. After one hour I finally understand your expression :-) . Regards -- Michael Strey www.strey.biz
[O] [BUG, LaTeX] LATEX_CLASS_OPTIONS don't always work
This is a minor issue.
The replacement of LaTeX class options by
#+LATEX_CLASS_OPTIONS: [ngerman]
doesn't work if the documentclass definition in org-latex-classes
consists of more than one line.
I used such a definition in my Koma-script letters:
\documentclass[%
fontsize=11pt,%
strey_consult,%
c4envelope, % optional
]{scrlttr2}
For such a definition the replacement doesn't work.
If I reduce the LaTeX expression to one line, everything is fine.
I tracked down the issue to the regular expression in
(if class-options
(replace-regexp-in-string
^[ \t]*documentclass\\(\\[.*?\\]\\)
class-options header t nil 1)
header)
Here I gave up for today.
Regards
--
Michael Strey
www.strey.biz
Re: [O] BBDB(3) or org-contacts
On Wed, Jan 09, 2013 at 03:16:09PM +0100, Gour wrote:
[...]
I use this as Customer Relationship Management (CRM) system.
...and would like to use it as CRM as well. Can you, please, share some
more info about your setup (I'll probably use Gnus instead of Mutt)?
Here is my YASnippet template for the organisation
,
| #name : Contact Organisation
| #key : org
| #contributor : Michael Strey [EMAIL PROTECTED]
| # --
| ** ${1:organisation}
| :PROPERTIES:
| :KIND: org
| :ORG: $1;${2:devision}
|
:ADR;TYPE=work:${3:adr1};${4:adr2};${5:adr3};${6:city};${7:state};${8:zip_code};${9:country}
| :EMAIL:mailto:${10:company_email}
| :TEL;PREF=1;TYPE=voice,work:[[tel:${11:tel}]]
| :TEL;TYPE=fax,work:[[tel:${12:fax}]]
| :URL: http://$13
| :LANG: $14
| :END:
| $0
| Added: [`(org-read-date nil nil +0d)`]
`
and here that for a contact in the next sub-level
,
| #name : Contact Individual
| #key : contact
| #contributor : Michael Strey [EMAIL PROTECTED]
| # --
| *** ${1:surname}, ${2:name}
| :LOGBOOK:
| - Added: [`(org-read-date nil nil +0d)`]
| :END:
|
| :PROPERTIES:
| :KIND: individual
| :ORG: ${3:organisation};${4:devision}
| :TITLE:${5:title}
| :FN: $2 $1
| :N:$1;$2;;
| :NICKNAME: $19 $1
|
:ADR;TYPE=work:${6:adr1};${7:adr2};${8:adr3};${9:city};${10:state};${11:zip_code};${12:country}
| :EMAIL:mailto:${13:company_email}
| :TEL;PREF=1;TYPE=voice,work:[[tel:${14:tel}]]
| :TEL;TYPE=voice,cell:[[tel:${15:mobile}]]
| :TEL;TYPE=fax,work:[[tel:${16:fax}]]
| :URL: http://$17
| :LANG: $18
| :END:
| $0
`
For my private contacts I have a simpler template
,
| #name : Contact Individual (private)
| #key : privat
| #contributor : Michael Strey [EMAIL PROTECTED]
| # --
| *** ${1:surname}, ${2:name}
| :PROPERTIES:
| :KIND: individual
| :FN: $2 $1
| :N:$1;$2;;
| :NICKNAME: ${3:salutation}
|
:ADR;TYPE=home:;;${4:adr3};${5:Dresden};${6:Sachsen};${7:zip_code};${8:Deutschland}
| :EMAIL:mailto:${9:email}
| :TEL;PREF=1;TYPE=voice,home:[[tel:${10:tel}]]
| :TEL;TYPE=voice,cell:[[tel:${11:mobile}]]
| :LANG: ${12:de}
| :END:
| $0
| Added: [`(org-read-date nil nil +0d)`]
`
The LOGBOOK drawer is used to store log notes with C-c C-z. In the lead
phase, as long as I do not have a dedicated sales project with a contact
or organisation, I store all notes below the individual or organisation
respectively.
As soon as there is a real chance to sell something, I define a sales
project in a second file containing all of my sales projects. Here
comes the YASnippet for such a project.
,
| #name : Sales Project
| #key : salesp
| #contributor : Michael Strey [EMAIL PROTECTED]
| # --
| *** PENDING ${1:customer} -- ${2:product}
:SP:
| :PROPERTIES:
| :Customer: $1
| :Vendor: ${3:vendor}
| :Product: $2
| :Quantity_short: ${4:quantity}
| :Quantity_long: ${5:quantity_long}
| :Price:${6:price}
| :Rate: ${7:0.1}
| :Probability: ${8:0.5}
| :PlannedDeliveryDate:
| :Delivered: [ ]
| :Invoices: [ ]
| :Payed:[ ]
| :COLUMNS: %Customer %Product %Price %Quantity_short(Qty$_1$)
%Probability(Prob.) %Value1(Value) %Quantity_long(Qty$_2$) %Value2(Potential)
| :END:
| Added: [`(org-read-date nil nil +0d)`]
| Last update: [`(org-read-date nil nil +0d)`]
| #+BEGIN: columnview :hlines 1 :maxlevel 3 :id local
| | Customer | Product | Price | Qty$_1$ | Prob. | Value | Qty$_2$ | Potential |
| |--+-+---+-+---+---+-+---|
| | Hyundai | VEGA| 1 | 1 | 0.5 | 5000 | 1 | 1 |
| #+TBLFM: \$6=\$3*\$4*\$5;%.0f::\$8=\$3*\$7;%.0f
| #+END:
| Outcome
| $0
| Contacts
| [[file:contacts.org::${9:surname}, ${10:name}][$10 $9]]
| Documents
:noexport:
| Results
:noexport:
| - [ ] Result
| - [ ] Link to following project
| - [ ] Ask for recommendations
| - [ ] Link to competitor(s)
| - [ ] Archiving (later) into external file
| Log
`
Thus in general contacts.org is uses only for the contacts. Projects
from salesprojects.org contain links to these contacts. Links to
e-mails are stored in the sales projects (section Log) as well.
Regards
--
Michael Strey
www.strey.biz
Re: [O] BBDB(3) or org-contacts
On Tue, Jan 08, 2013 at 05:14:43PM +0100, Daniel Clemente wrote: [...] Therefore I use its infrastructre (because I like it) but I don't run its code. I'll explain myself: I keep this structure in an .org file: ** John von Neumann :mathematic: :PROPERTIES: :EMAIL:j...@neumann.com :END: - some info 1+ I've more than 1000 contacts and this system works well and with reasonable speed. For integration with mutt, I use Karl Voit's lbdb module for org-contact [fn:1]. I've defined a set of properties derived from the VCard specification and like Daniel, I have a Capture template to create new organisations and contacts below them. I use this as Customer Relationship Management (CRM) system. Footnotes: [fn:1] http://lists.gnu.org/archive/html/emacs-orgmode/2011-10/msg01059.html Regards -- Michael Strey www.strey.biz
Re: [O] A mail client that is org-mode compatible
On Wed, Jan 02, 2013 at 01:07:20PM -0600, Robert Goldman wrote: I use multiple devices, so I need to have an IMAP server that really is an IMAP server, instead of something the just serves up messages to be downloaded. I have multiple folders, and I read messages from different clients. I have a similar requirement. My setup consists of mutt together with imapfilter for sorting and filtering of e-mail on the IMAP server and offlineimap to hold a copy of all mails on the IMAP server locally. For the integration into the org-mode workflow, I have defined a [[mutt: ]] link and installed a script to capture a mail from mutt. To show a mail in Emacs, I use notmuch. It works very well for me. Although I have to say that I'm coming from the Vi world and using mutt since many years. So this cumbersome setup was my concession to keep my familiar e-mail client. The following link may help with a similar (but probably easier) setup with wanderlust that provides better and easier integration into Emacs. http://emacs-fu.blogspot.de/search/label/wanderlust Regards -- Michael Strey www.strey.biz
Re: [O] [OT] Org spotted in the wild
On Tue, Sep 18, 2012 at 08:25:55AM +0200, Bastien wrote: Loris Bennett loris.benn...@fu-berlin.de writes: http://mosh.mit.edu/ I must admit that I designed the new website based on the one above. The result is not as neat, but close enough. mosh.mit.edu was built with the Twitter Bootstrap CSS framework. See http://twitter.github.com/bootstrap/. -- Michael Strey mailto:mst...@strey.biz http://www.strey.biz
Re: [O] Org/LaTeX set-up for business letters?
Hi Thorsten, On Fri, Jul 06, 2012 at 12:47:59AM +0200, Thorsten Jolitz wrote: suvayu ali fatkasuvayu+li...@gmail.com writes: ... [1] Off the top of the head I recall a package called `scrlttr'. Yes, part of KOMA (?), but thats rather low level if you have to design your own letters - and who knows all that stuff about professional letter design?... Letter styles may be very different from country to country. Thus the LaTeX world knows various attempts to create templates for letters that comply with national standards and national fancy. Just for the case that you are German, have a look at www.komascript.de and look for the examples from Markus Kohms KOMA-Script book. There are several examples how to use the scrlttr2 class and how to tweak it to create an individual template. -- Regards Michael
Re: [O] Regression in `org-todo'
Hi Moritz Bastien, This bug fix seems not to be complete. At least switching the todo state in repeated tasks and in conjunction with org-checklist didn't work for me as it used to before the last update. PFA a patch that solved the problem for me. ATTENTION: Please check this patch very carefully. This is my first contribution to org-mode and my first patch ever. My lisp knowledge is rudimentary and I do not really understand the code. Thanks to all developers for your work! Best regards Michael Strey On Sun, Apr 01, 2012 at 05:01:12PM +0200, Moritz Ulrich wrote: Commit 6cbf1f417222321a47848a7368427ba8a22fe3a5 renames variable `last-state' to `org-last-state' in org.el. This change isn't reflected in function `org-todo'. That causes the following regression: Toggling a TODO state to DONE on a headline via C-c C-t (`org-todo') results in: Symbol's value as variable is void: org-last-state. This is reproducible in latest HEAD and even in tag 'release_7.8.07'. M-x emacs-version: GNU Emacs 24.0.94.1 (i386-apple-darwin11.3.0, NS apple-appkit-1138.32) of 2012-03-12 on moritz-macbook.local The attached patch contains a simple (two line) fix. From 554b1ece898c9aaff47e729d6fa746ec21b5eefd Mon Sep 17 00:00:00 2001 From: Michael Strey mst...@strey.biz Date: Mon, 2 Apr 2012 16:21:34 +0200 Subject: [PATCH] s/state/org-state/ --- contrib/lisp/org-checklist.el |2 +- lisp/org.el | 14 +++--- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/contrib/lisp/org-checklist.el b/contrib/lisp/org-checklist.el index a974874..03c7547 100644 --- a/contrib/lisp/org-checklist.el +++ b/contrib/lisp/org-checklist.el @@ -129,7 +129,7 @@ of checkbox items (a2ps-buffer) (defun org-checklist () - (when (member state org-done-keywords) + (when (member org-state org-done-keywords) (org-make-checklist-export) (org-reset-checkbox-state-maybe))) diff --git a/lisp/org.el b/lisp/org.el index 9183743..bf30497 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -2429,7 +2429,7 @@ When nil, only the date will be recorded. (defcustom org-log-note-headings '((done . CLOSING NOTE %t) -(state . State %-12s from %-12S %t) +(org-state . State %-12s from %-12S %t) (note . Note taken on %t) (reschedule . Rescheduled from %S on %t) (delschedule . Not scheduled, was %S on %t) @@ -2458,7 +2458,7 @@ agenda log mode depends on the format of these entries. (cons (const :tag Heading when closing an item done) string) (cons (const :tag Heading when changing todo state (todo sequence only) - state) string) + org-state) string) (cons (const :tag Heading when just taking a note note) string) (cons (const :tag Heading when clocking out clock-out) string) (cons (const :tag Heading when an item is no longer scheduled delschedule) string) @@ -11437,10 +11437,10 @@ For calling through lisp, arg is also interpreted in the following way: ;; It is now done, and it was not done before (org-add-planning-info 'closed (org-current-effective-time)) (if (and (not dolog) (eq 'note org-log-done)) - (org-add-log-setup 'done state this 'findpos 'note))) + (org-add-log-setup 'done org-state this 'findpos 'note))) (when (and org-state dolog) ;; This is a non-nil state, and we need to log it - (org-add-log-setup 'state org-state this 'findpos dolog))) + (org-add-log-setup 'org-state org-state this 'findpos dolog))) ;; Fixup tag positioning (org-todo-trigger-tag-changes org-state) (and org-auto-align-tags (not org-setting-tags) (org-set-tags nil t)) @@ -11938,7 +11938,7 @@ This function is run automatically after each state change to a DONE state. (org-todo-log-states nil) re type n what ts time to-state) (when repeat - (if (eq org-log-repeat t) (setq org-log-repeat 'state)) + (if (eq org-log-repeat t) (setq org-log-repeat 'org-state)) (setq to-state (or (org-entry-get nil REPEAT_TO_STATE) org-todo-repeat-to-state)) (unless (and to-state (member to-state org-todo-keywords-1)) @@ -11955,7 +11955,7 @@ This function is run automatically after each state change to a DONE state. ;; make sure we take a note, not only a time stamp (setq org-log-note-how 'note)) ;; Set up for taking a record - (org-add-log-setup 'state (or done-word (car org-done-keywords)) + (org-add-log-setup 'org-state (or done-word (car org-done-keywords)) org-last-state 'findpos org-log-repeat))) (org-back-to-heading t) @@ -12377,7 +12377,7 @@ EXTRA is additional text that will be inserted
Re: [O] Regression in `org-todo'
Hi Bastien, On Mon, Apr 02, 2012 at 05:03:04PM +0200, Bastien wrote: ... Please test against latest HEAD and tell me if your problem is still here, it shouldn't. I confirm that the problem is solved. Thank you! It's interesting to see how a bug in a module from the contrib path can cause strange behaviour of org-mode's core functions. Best regards Michael Strey
