Re: [O] [OT] Gnus mail tutorial?
Marcin Borkowski writes: I'm thinking about using Emacs as my email client, and I'm considering using Gnus for that. If it is Emacs rather than Gnus itself that attracts you, then you might consider notmuch or mu4e. Both have a Xapian-based core, and include an Emacs interface.
Re: [O] [OT] Gnus mail tutorial?
John Hendy jw.he...@gmail.com writes: On May 24, 2013 6:01 PM, Marcin Borkowski mb...@wmi.amu.edu.pl wrote: Hi list, sorry for an off-topic question, but I'm sure someone here will be able to help me with this: I'm thinking about using Emacs as my email client, and I'm considering using Gnus for that. The Gnus manual is a bit intimidating; is there any newbie-friendly tutorial which might help get me started, taking into account that I do /not/ want to use Gmail, but another (IMAP-aware) mail service? Seconded. I tried following the tutorials that *do* exist once and just gave up. Something tried and known to work and be complete would be awesome. and I know there's a lot of gnus users on the list :) I know the OP explicitly does not want to use gmail, however this gmail solution is *very* concise and should be easily adapted to work with a non-gmail imap service. http://www.emacswiki.org/emacs/GnusGmail#toc2 Just replace the gmail urls and ports with those of the service you want to use. Also, note that in blocks like the following (setq gnus-select-method '(nnimap gmail (nnimap-address imap.gmail.com) (nnimap-server-port 993) (nnimap-stream ssl))) in the 'nnimap gmail' portion the gmail is just a name, not something special, and it can be replaced with any arbitrary string. The starter-kit-gnus page of my starter kit may be helpful, however, it doesn't provide much new information beyond that available at the previous emacs wiki page. http://eschulte.github.io/emacs24-starter-kit/starter-kit-gnus.html https://raw.github.com/eschulte/emacs24-starter-kit/master/starter-kit-gnus.org Hope this helps, John Regards, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] [OT] Gnus mail tutorial?
Marcin Borkowski mb...@wmi.amu.edu.pl writes: Hi list, sorry for an off-topic question, but I'm sure someone here will be able to help me with this: I'm thinking about using Emacs as my email client, and I'm considering using Gnus for that. The Gnus manual is a bit intimidating; is there any newbie-friendly tutorial which might help get me started, taking into account that I do /not/ want to use Gmail, but another (IMAP-aware) mail service? Hi Marcin, For me Gnus is the gold standard among mail/news clients. It can be hard work to set it up but it is worth it. Alas, some good resources have actually vanished from the web over the years. Sacha Chua describes a very basic set up for IMAP here: http://sachachua.com/blog/2008/05/geek-how-to-use-offlineimap-and-the-dovecot-mail-server-to-read-your-gmail-in-emacs-efficiently/ If you are not running /Sendmail/Postfix/Exim etc you may find this page helpful http://www.emacswiki.org/emacs/SendingMail There are of course several Gnus mailing lists/newsgroups. Good luck! Glyn
[O] [PATCH] org.el: Don't flyspell check within source code blocks
Hi, list. I recently started using flyspell, but I wasn't pleased with the spell checking in my source code blocks. After digging a bit for a solution, I found a post to the list with a nice solution[0]. However, it seems no patch was ever submitted. So, here goes. If there's a deeper reason this part of the code was never changed, please enlighten me. I didn't see any further mailing list discussion, so I assumed it was still fair game. Thanks, Trevor [0]: http://lists.gnu.org/archive/html/emacs-orgmode/2012-12/msg00764.html
[O] [PATCH] org.el: Don't flyspell check within source code blocks
* lisp/org.el (org-mode-flyspell-verify): Check if `org-element-at-point' is of type `src-block', and don't flyspell if that's the case. TINYCHANGE --- lisp/org.el | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index 94078f9..81428f5 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -23596,7 +23596,8 @@ To get rid of the restriction, use \\[org-agenda-remove-restriction-lock]. (not (member-ignore-case word (org-get-export-keywords))) (not (member-ignore-case word (mapcar 'car org-element-block-name-alist))) -(not (member-ignore-case word '(BEGIN END ATTR)) +(not (member-ignore-case word '(BEGIN END ATTR))) +(not (not (eq (org-element-type (org-element-at-point)) 'src-block)) (defun org-remove-flyspell-overlays-in (beg end) Remove flyspell overlays in region. -- 1.8.2.3
Re: [O] [PATCH] org.el: Don't flyspell check within source code blocks
Ack, what? Please disregard, I slipped a double negative in somehow. On Sat, May 25, 2013 at 3:17 AM, Trevor Murphy trevor.m.mur...@gmail.comwrote: * lisp/org.el (org-mode-flyspell-verify): Check if `org-element-at-point' is of type `src-block', and don't flyspell if that's the case. TINYCHANGE --- lisp/org.el | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index 94078f9..81428f5 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -23596,7 +23596,8 @@ To get rid of the restriction, use \\[org-agenda-remove-restriction-lock]. (not (member-ignore-case word (org-get-export-keywords))) (not (member-ignore-case word (mapcar 'car org-element-block-name-alist))) -(not (member-ignore-case word '(BEGIN END ATTR)) +(not (member-ignore-case word '(BEGIN END ATTR))) +(not (not (eq (org-element-type (org-element-at-point)) 'src-block)) (defun org-remove-flyspell-overlays-in (beg end) Remove flyspell overlays in region. -- 1.8.2.3
[O] [PATCH] Take 2 on org.el: Don't flyspell check within source code blocks
Very sorry about the email spam. This fixes the blindingly obvious double negative in my previous submission. Thanks, Trevor
[O] [PATCH] org.el: Don't flyspell check within source code blocks
* lisp/org.el (org-mode-flyspell-verify): Check if `org-element-at-point' is of type `src-block', and don't flyspell if that's the case. TINYCHANGE --- lisp/org.el | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index 94078f9..ce48bb0 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -23596,7 +23596,8 @@ To get rid of the restriction, use \\[org-agenda-remove-restriction-lock]. (not (member-ignore-case word (org-get-export-keywords))) (not (member-ignore-case word (mapcar 'car org-element-block-name-alist))) -(not (member-ignore-case word '(BEGIN END ATTR)) +(not (member-ignore-case word '(BEGIN END ATTR))) +(not (eq (org-element-type (org-element-at-point)) 'src-block) (defun org-remove-flyspell-overlays-in (beg end) Remove flyspell overlays in region. -- 1.8.2.3
Re: [O] [OT] Gnus mail tutorial?
Glyn Millington writes: For me Gnus is the gold standard among mail/news clients. It can be hard work to set it up but it is worth it. Alas, some good resources have actually vanished from the web over the years. Can Gnus be directly used with local mail in maildir format? If so, one could easily switch between clients. Alan
Re: [O] [PATCH] ox-koma-letter.el: Reintroduce variables removed in commit 832c6fd with proper defaults (was Re: [patch] ox-koma-letter.el: clean-up/semantic bug [4/4])
Hi Robert,
Robert Klein wrote:
Hi,
FWIW, from a users view it would be nice if:
- Use Author/Email information from org file
- If not present use information from LCO file
- if neither org file nor LCO file has any information use
user-full-name and user-email-address
Could this be solved by having several e.g. `setkomavar{fromname}'
and so on in the tex file, so is created as follows:
if no #+AUTHOR in org-file and user-full-name is set:
add user-full-name
if #+LCO(s) in org-file:
add LCO file(s)
if #+AUTHOR in org-file:
add \setkomavar{fromname}{#+AUTHOR}
same for email
add \setkomavar{signature}{\usekomavar{fromname}}
This is what is implemented by the latest patch
(http://thread.gmane.org/gmane.emacs.orgmode/72430/focus=72525).
so the result tex file may have:
\setkomavar{fromname}{Hans Wurst}
\setkomavar{fromemail}{hans_wu...@example.com}
...
\setkomavar{fromname}{Reiner Zufall}
\setkomavar{fromemail}{reiner_zuf...@example.com}
\setkomavar{signature}{\usekomavar{fromname}}
Why do you repeat fromname and fromemail in your example?
Cheers,
Viktor
This probably isn't a `clean' solution, but should work without a need
to grep LCO files.
Best regards
Robert
On 05/23/2013 12:06 AM, Viktor Rosenfeld wrote:
Hi Rasmus,
Viktor Rosenfeld wrote:
Hi Rasmus,
Rasmus wrote:
Viktor Rosenfeld listuse...@gmail.com writes:
Or 5, keep the change from SENDER to AUTHOR but revert the default
values to `org-koma-letter-*' variables. (Right now the AUTHOR and EMAIL
lines could be removed because they duplicate the derived latex
backend.)
I once had a teacher who talked about the optimal degree of
conservatism (as well speaking positively about being in the infamoues
ivory tower). 5. is fine with me. So I guess the deal is
1. default value is the same as in ox-latex.
2. . . . but it's kept in a seperete variable ox-kl variable.
I think that switching from SENDER to AUTHOR, keeping the
`org-koma-letter-{author,email}' variables in the KOMA backend, but
setting them per default to `user-full-name' and `user-mail-address',
would solve both your problems and let me keep LCO files. I would then
simply set these `org-koma-letter-*' variables to `nil' and document
this setup in the docstring. I'll see tomorrow if this is feasable.
Does the attached patch work for you (also with ps tags?)
It works, but I noticed the following problem: According to the Emacs
documentation `user-mail-address' is only set by Emacs after the
initialization process has completed and if it is not explicitly set
during initialization [1]. So, the defcustom of org-koma-letter-email
does not work as expected if the user has not set `user-mail-address'
before. Instead it is set to the empty string, which according to the
code setting `user-mail-address' means not set yet.
This can be taking care of by using `after-init-hook' as in the example
below. It has the added advantage that the value of `user-mail-address'
will be picked up regardless of whether it is set before or after
require'ing ox-koma-letter.
Note that this creates a slight inconsistency with regard to
`user-full-name' which is only picked up correctly if it is set before
require'ing ox-koma-letter. I've fixed this by a slightly complicated
defcustom definition of `org-koma-letter-author' and another
after-init-hook.
I've also changed the docstring to indicate what are the default values
and added the :group and :type flags again.
I've put my changes into a patch against the current master (commit
06cdb2d2). Could you check it with your setup?
Cheers,
Viktor
[O] Bug: org-meta-return in narrowed buffer makes the last line invisible
Hi, In my current environment, org-meta-return seems to make the last line of a buffer invisible if the buffer is narrowed. At first I thought the lines are gone but that was false. All text are there but you can't see it. First, here is my environment: - Org-mode version 8.0.3 (release_8.0.3-150-g61d8eb @ /home/yashi/src/org-mode/lisp/) - GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.4.2) of 2013-04-14 on trouble, modified by Debian - uname -a: Linux leno 3.8-2-amd64 #1 SMP Debian 3.8.13-1 x86_64 GNU/Linux - Debian Sid Second, here is my step to reproduce: 1. create a file with the following lines: #+BEGIN_SRC org ,* head ,** the last line in the narrow ,* the last line #+END_SRC 2. emacs -Q 3. open the above file 4. narrow the buffer at 'head' with org-narrow-to-subtree to make the contents as below: #+BEGIN_SRC org ,* head ,** the last line in the narrow #+END_SRC 5. org-meta-enter at the end of the first line. this makes the visible contents to be #+BEGIN_SRC org ,* head ,** the last line in the nar #+END_SRC notice that narrow became nar Is this reproducible? Does anyone see this bug? Thanks, -- yashi
Re: [O] [PATCH] ox-koma-letter.el: Reintroduce variables removed in commit 832c6fd with proper defaults (was Re: [patch] ox-koma-letter.el: clean-up/semantic bug [4/4])
Hello,
Viktor Rosenfeld writes:
Hi Robert,
Robert Klein wrote:
Hi,
FWIW, from a users view it would be nice if:
- Use Author/Email information from org file
- If not present use information from LCO file
- if neither org file nor LCO file has any information use
user-full-name and user-email-address
Could this be solved by having several e.g. `setkomavar{fromname}'
and so on in the tex file, so is created as follows:
if no #+AUTHOR in org-file and user-full-name is set:
add user-full-name
if #+LCO(s) in org-file:
add LCO file(s)
if #+AUTHOR in org-file:
add \setkomavar{fromname}{#+AUTHOR}
same for email
add \setkomavar{signature}{\usekomavar{fromname}}
This is what is implemented by the latest patch
(http://thread.gmane.org/gmane.emacs.orgmode/72430/focus=72525).
I'm waiting for Rasmus's confirmation that it works for him before
committing it.
Alan
Re: [O] [OT] Gnus mail tutorial?
Alan Schmitt alan.schm...@polytechnique.org writes: Glyn Millington writes: For me Gnus is the gold standard among mail/news clients. It can be hard work to set it up but it is worth it. Alas, some good resources have actually vanished from the web over the years. Can Gnus be directly used with local mail in maildir format? If so, one could easily switch between clients. The bigger bugs for me in gnus is its inferior maildir support: it fail to properly mark mail as read, it use its own meta-data file that can cause problem to other mail client Hence the configs (as Sacha Chua does) where one use dovecot to read maildir, letting gnus to connect to dovecot instead of reading maildir directly. -- Rémi Vanicat
[O] Babel post-processing and export problem
Hello,
I'm trying to post-process a LaTeX code block, so that the evaluated results
gets framed on export.
While almost working, my trials fail, because the results of the code block
gets wrapped in a table:
| \begin{mdframed} || |
| \begin{itemize} || |
| \item| Item | a|
| \begin{itemize} || |
| \item| Deeper | item |
| \end{itemize}|| |
| \end{itemize}|| |
| \end{mdframed} || |
Here an ECM demo'ing the problem:
--8---cut here---start-8---
#+TITLE: ECM
#+AUTHOR:Seb Vauban
#+OPTIONS: H:2
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [presentation,t]
#+BEAMER_THEME: Madrid
#+LaTeX_HEADER: \usepackage{mdframed}
#+LaTeX_HEADER: \mdfsetup{linecolor=gray!40,linewidth=.4pt,%
#+LaTeX_HEADER: innertopmargin=0.4em, innerrightmargin=0.4em,%
#+LaTeX_HEADER: innerbottommargin=0.4em, innerleftmargin=0.4em}
* Syntax
** Hidden code :noexport:
#+name: frameit
#+begin_src sh :var data= :results output verbatim
echo \begin{mdframed}
echo $data
echo \end{mdframed}
#+end_src
** Post-process the results
I want to display the results of *this LaTeX code's interpretation* inside a
framebox, so that it clearly stands out from the rest of the document.
#+name: latexcode
#+begin_src latex :exports both :post frameit(data=*this*) :results verbatim
\begin{itemize}
\item Item a
\begin{itemize}
\item Deeper item
\end{itemize}
\end{itemize}
#+end_src
** Results...
#+results: latexcode
#+BEGIN_LaTeX
\begin{mdframed}
\begin{itemize}
\item Item a
\begin{itemize}
\item Deeper item
\end{itemize}
\end{itemize}
\end{mdframed}
#+END_LaTeX
However, while the results in the Org buffer (here, just above) is correct,
the one at the export time is not: it is table'd.
Having explicitly put verbatim for the results does not help.
Any idea??
--8---cut here---end---8---
Best regards,
Seb
--
Sebastien Vauban
[O] How to define the one-line export-block for certain exporter backend?
Hi, I learned from ox-html.el that the #+BEGIN_HTML #+END_HTML block can be associated with a function by the :export-block argument in org-export-define-backend. But it seems doesn't apply to the #+HTML: block. Could someone tell me how to define a one-line export-block for specific exporter, like #+HTML: does for ox-html.el? Regards, Yujie
Re: [O] Indentation of code blocks within lists
Hello, Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Indeed. I have as well `org-src-preserve-indentation' set to `t', for the same reason as pointed out: if I don't use it that way, then my code blocks which have different relative depths are exported (in HTML) on the same level, as if there was no indentation to respect. So, yes, it does work if you don't need to preserve indentation, you're well right. But, if not, the indentation is lost on export (and on source editing with C-c '). I have pushed a fix on maint (at least for the export part, the source editing one is another story). Could you confirm it behaves as expected? Regards, -- Nicolas Goaziou
Re: [O] Error with \usepackage{amsmath} due to \iint already being defined
On Fri, May 24, 2013 at 02:38:42PM -0400, Nick Dokos wrote:
The wasysym docs say that there should be no conflict, but that seems
to be wrong: ISTR multiple instances of this conflict.
If you prefer the amsmath integral signs over the wasysym ones, then
probably the best thing to do is to load wasysym with the
``nointegrals'' option:
\usepackage[nointegrals]{wasysym}
This can be done permanently by customizing
org-latex-default-packages-alist and adding the option to the wasysym
entry.
I have been using the following for quite a few years.
;;; LaTeX export customisations
;; hack for error free latex export with amsmath
;; remove when defaults are changed in the future
(setcar (rassoc '(wasysym t) org-latex-default-packages-alist)
nointegrals)
(add-to-list 'org-latex-packages-alist '( amsmath t))
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Per file ID
On Fri, May 24, 2013 at 04:43:53PM +0200, Klaus-Dieter Bauer wrote: Hello! I intend to use org-mode for organizing my research notes; I prefer however a wiki style with many files rather than one big file. I found that the ID mechanism is quite robust for linking across files, but most of the time I'd like to link to a file, not a heading in that file, by ID. Is that possible in org-mode? The motivation behind id links is their guaranteed uniqueness. For linking to files, doesn't simply using filenames do that? [[file:path/to/file.org][My notes]] Why reinvent the wheel? ;) Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] [PATCH] ox-koma-letter.el: Reintroduce variables removed in commit 832c6fd with proper defaults (was Re: [patch] ox-koma-letter.el: clean-up/semantic bug [4/4])
Alan Schmitt alan.schm...@polytechnique.org writes:
Hello,
Viktor Rosenfeld writes:
Hi Robert,
Robert Klein wrote:
Hi,
FWIW, from a users view it would be nice if:
- Use Author/Email information from org file
- If not present use information from LCO file
- if neither org file nor LCO file has any information use
user-full-name and user-email-address
Could this be solved by having several e.g. `setkomavar{fromname}'
and so on in the tex file, so is created as follows:
I'd go with 'no'. It's not aesthetically pleasing and I don't want my
output to look like LyX. When feasible we should go for beautiful
output. This isn't always the case at the moment, but still.
if no #+AUTHOR in org-file and user-full-name is set:
add user-full-name
if #+LCO(s) in org-file:
add LCO file(s)
if #+AUTHOR in org-file:
add \setkomavar{fromname}{#+AUTHOR}
same for email
Currently the ordering is: #+AUTHOR #+LCO and AUTHOR default to
(user-full-name).
On a side-note, Viktor: this seems to be the default in scrletter
anyway:
add \setkomavar{signature}{\usekomavar{fromname}}
Could we remove it? I'd like us to get to a more clean template (C-e
# koma-letter RET).
This is what is implemented by the latest patch
(http://thread.gmane.org/gmane.emacs.orgmode/72430/focus=72525).
I'm waiting for Rasmus's confirmation that it works for him before
committing it.
Thanks and sorry for the wait. No it didn't work for me. My user
name was always overwritten by . . . I couldn't figure out why.
I've attached a patch that work for me (it goes on top of Viktor's
patch 148c737ae79f3a98d8e93147c2d0ec0db3a2389a). It allows for nil
and it gets up-to-date default values by default. In my book it's a
bit more clean 'cause it doesn't rely on hooks. It does, introduce a
new helper function to distinguish between a function value (which are
default for the two variables) and a string value (and nil for that
matter). I don't know if this is undesirable. It would crash if you
set the variables to a symbol that isn't nil and isn't a function.
It seems to work in mine and Viktor's use-case (to the best of my
testing ability).
–Rasmus
--
⠠⠵
Re: [O] scale inline images in orgmode
Bastien bzg at altern.org writes: Hi Alexander, AW alexander.willand at t-online.de writes: If I include an image in an *.org file, let's say [[large-image.jpg]], I can toggle the inline image with C-c C-x C-v . You can now (from git master) use `org-image-actual-width'. (setq org-image-actual-width 300) = always resize inline images to 300 pixels (setq org-image-actual-width '(400)) = if there is a #+ATTR.*: width=200, resize to 200, otherwise resize to 400 (setq org-image-actual-width nil) = if there is a #+ATTR.*: width=200, resize to 200, otherwise don't resize (setq org-image-actual-width t) = Never resize and use original width (the default) HTH, Hello! I am searching for a while now for a solution to get image scaling inside the org-mode buffer working /on Windows/. After installing GnuWin32 at least displaying the various image types works, but scaling does not. I assume the problem simply is missing ImageMagick-support in the Windows binaries. Any idea, how to get it? Or how to check whether emacs was compiled with ImageMagick support and just can't find DLLs on my system? Note: I am also trying a while now to get emacs compiling from source, but there are so many problems popping up, that I barely see a chance to get this working. I am using org-mode 8.0.3-15-g030e96-elpa GNU Emacs 24.3.1 (i386-mingw-nt6.1.7601) of 2013-03-17 on MARVIN Windows 7 Home Premium, 64bit kind regards, Klaus
[O] Build-System: Why not compile contrib
Hi. I'm using the maint branch of org-mode and lately I discovered that the files beneath contrib are not compiled and there seems to be no easy way (e.g. via local.mk) to enable compilation of contrib. Is this on purpose and if yes: why? -- Stefan.
Re: [O] How to define the one-line export-block for certain exporter backend?
Hello, Yujie Wen yjwen...@gmail.com writes: Could someone tell me how to define a one-line export-block for specific exporter, like #+HTML: does for ox-html.el? Simply not ignore the keyword in the function transcoding keywords (see `org-html-keyword'). Regards, -- Nicolas Goaziou
[O] tag groups
Hi all, I have a problem about groups of tags. In my custom-file, I defined : '(org-tag-alist (quote ((projet . 112) (suspendu . 122) (:startgroup lieu) (@dehors . 100) (:grouptags) (@lieu1 . 97) (@lieu2 . 118) (:endgroup '(org-tag-faces nil) '(org-tag-persistent-alist (quote ((note . 110) (noexport . 120) (lien . 98) (crypt . 99 '(org-tags-exclude-from-inheritance (quote (crypt))) '(org-tags-match-list-sublevels (quote indented)) Now, I get value for : org-tag-alist ((projet . 112) (suspendu . 122) (:startgroup lieu) (@dehors . 100) (:grouptags) (@lieu1 . 97) (@lieu2 . 118) (:endgroup)) value for : org-tag-persistent-alist ((note . 110) (noexport . 120) (lien . 98) (crypt . 99)) value for : org-tag-alist-for-agenda ((:startgroup) (prêté . 112) (emprunté . 101) (:endgroup) (note . 110) (noexport . 120) (lien . 98) (crypt . 99) (projet . 112) (suspendu . 122) (:startgroup lieu) (@dehors . 100) (:grouptags) (@lieu1 . 97) (@lieu2 . 118)) org-tag-groups-alist org-tag-groups-alist-for-agenda keep their original value : nil If I filter by tag @dehors, I do not get the new filter by tags @dehors or @lieu1 or @lieu2. Versions : GNU Emacs 24.3.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.4.2) of 2013-05-11 on gkar, modified by Debian Org-mode version 8.0.3 (release_8.0.3-150-g61d8eb @ /home/momo/.emacs.d/vendor/org-mode/lisp/) Thanks, Maurice
[O] format for clocktable
Hi, I recently switched from org-mode 6.xx to 8.0.3. I used to have results = 24:00 in the form of 34:59 for example, not 1d 10:59 - see below I do not manage to get back the old format, which is more convenient for me. The manual mention a :formatter switch, but I have not found information about this yet Thank for your help J #+BEGIN: clocktable :maxlevel 4 :emphasize nil :scope file :block week #+CAPTION: Clock summary at [2013-05-25 Sat 17:09], for week 2013-W21. | Headline | Time | | | |---++--+---| | *Total time* | *1d 10:59* | | | |---++--+---| | Journal | 1d 10:59 | | | | \__ Mai || 1d 10:59 | | | \_ [2013-05-24 Fri] || | 6:15 | | \_ [2013-05-23 Thu] || | 13:08 | | \_ [2013-05-22 Wed] || | 7:46 | | \_ [2013-05-21 Tue] || | 7:50 | #
Re: [O] format for clocktable
Hi Jean, Jean Wallemacq jean.wallem...@skynet.be writes: Hi, I recently switched from org-mode 6.xx to 8.0.3. I used to have results = 24:00 in the form of 34:59 for example, not 1d 10:59 - see below I do not manage to get back the old format, which is more convenient for me. The manual mention a :formatter switch, but I have not found information about this yet What is the value of `org-time-clocksum-use-effort-durations' for you? C-h v org-time-clocksum-use-effort-durations RET Thanks, -- Bastien
Re: [O] [PATCH] org.el: Don't flyspell check within source code blocks
Hi Trevor, Trevor Murphy trevor.m.mur...@gmail.com writes: + (not (eq (org-element-type (org-element-at-point)) 'src-block) I think `org-in-src-block-p', while a bit less reliable, will be faster, and reliable/fast enough for this use-case. Let's see what others think/test. Thanks, -- Bastien
Re: [O] format for clocktable
value is nil in the screen, something is mentioned about some default value having been changed with emacs 24. My change to org 8.0.3 was made at the same time than an upgrade of emacs, so it may be linked to that. Further help is welcome ! Jean Le 25 mai 2013 à 17:50, Bastien b...@gnu.org a écrit : Hi Jean, Jean Wallemacq jean.wallem...@skynet.be writes: Hi, I recently switched from org-mode 6.xx to 8.0.3. I used to have results = 24:00 in the form of 34:59 for example, not 1d 10:59 - see below I do not manage to get back the old format, which is more convenient for me. The manual mention a :formatter switch, but I have not found information about this yet What is the value of `org-time-clocksum-use-effort-durations' for you? C-h v org-time-clocksum-use-effort-durations RET Thanks, -- Bastien
Re: [O] [PATCH] ox-koma-letter.el: Reintroduce variables removed in commit 832c6fd with proper defaults (was Re: [patch] ox-koma-letter.el: clean-up/semantic bug [4/4])
Hi Rasmus,
Rasmus wrote:
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.orgmode as well.
Alan Schmitt alan.schm...@polytechnique.org writes:
Hello,
Viktor Rosenfeld writes:
Hi Robert,
Robert Klein wrote:
Hi,
FWIW, from a users view it would be nice if:
- Use Author/Email information from org file
- If not present use information from LCO file
- if neither org file nor LCO file has any information use
user-full-name and user-email-address
Could this be solved by having several e.g. `setkomavar{fromname}'
and so on in the tex file, so is created as follows:
I'd go with 'no'. It's not aesthetically pleasing and I don't want my
output to look like LyX. When feasible we should go for beautiful
output. This isn't always the case at the moment, but still.
I agree that there should not be multiple instances of, e.g.,
\setkomavar{fromname} in the TeX file. I must have overlooked that bit
in the original mail.
On a side-note, Viktor: this seems to be the default in scrletter
anyway:
add \setkomavar{signature}{\usekomavar{fromname}}
Could we remove it? I'd like us to get to a more clean template (C-e
# koma-letter RET).
I think so, yes.
This is what is implemented by the latest patch
(http://thread.gmane.org/gmane.emacs.orgmode/72430/focus=72525).
I'm waiting for Rasmus's confirmation that it works for him before
committing it.
Thanks and sorry for the wait. No it didn't work for me. My user
name was always overwritten by . . . I couldn't figure out why.
Hmm, that's too bad. I tested it pretty thoroughly. Could you maybe
trace the contents of the variable by adding calls to message in various
places?
I've attached a patch that work for me (it goes on top of Viktor's
patch 148c737ae79f3a98d8e93147c2d0ec0db3a2389a). It allows for nil
and it gets up-to-date default values by default. In my book it's a
bit more clean 'cause it doesn't rely on hooks. It does, introduce a
new helper function to distinguish between a function value (which are
default for the two variables) and a string value (and nil for that
matter). I don't know if this is undesirable. It would crash if you
set the variables to a symbol that isn't nil and isn't a function.
Did you send the patch? I did not receive it and it's not available on
gmane.
Cheers,
Viktor
It seems to work in mine and Viktor's use-case (to the best of my
testing ability).
–Rasmus
--
⠠⠵
Re: [O] org-export, table.el complex tables, latex html
Hello, Uwe Brauer o...@mat.ucm.es writes: I have attached an org file which contains a complex table, which I generated partially with table.el. Now org-export can export this table *correctly* to latex, most likely using (table-generate-source 'latex table.latex Table), however org-export fails when exporting to html. Could this export option also please be implemented. Thanks Uwe Brauer This is a test table This is a test table Date: 2013-05-25 18:26:47 CEST Author: Uwe Brauer Org version 7.8.03 with Emacs version 21 You need to update Org. I cannot reproduce the problem on Org 8.0.3. Regards, -- Nicolas Goaziou
Re: [O] org-export, table.el complex tables, latex html
Nicolas == Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Uwe Brauer o...@mat.ucm.es writes: Org version 7.8.03 with Emacs version 21 You need to update Org. I cannot reproduce the problem on Org 8.0.3. Ok, I try. What's about orgtbl-to-latex does this work for you also? Uwe Brauer
[O] Xemacs 21.5.32 and org-8.03, compilation problems
Hello I know that compiling org under Xemacs is delicate. I succeeded with 7.8.3 but it seems that the installation process has changed quite a bit. I edit the relevant default.mk file (OK I should not do that but create local.mk) EMACS=/usr/local/bin/xemacs BATCH = $(EMACS) -batch -vanilla # Xemacs Now when running make the following problems showed up: - in almost all files the message: Symbol's value as variable is void: org-babel-temp-file Popped up - in org-footnote ** The following functions are not known to be defined: org-in-commented-line, org-in-indented-comment-line, org-inside-LaTeX-fragment-p, org-in-verbatim-emphasis, org-in-block-p, org-in-regexp, org-inside-latex-macro-p, org-trim, org-mark-ring-push, org-show-context, org-id-uuid, org-icompleting-read, org-back-over-empty-lines, org-fill-paragraph, org-end-of-subtree, outline-next-heading - org-list has similar complains, which I don't want to mention here - org.el itself: ! error ((Unknown keyword :package-version)) - ox-odt.el: !! File error ((Cannot open load file table)) Error occurred processing /home/oub/ALLES/xemacs/site-lisp/packages/org-8.0.3/lisp/ox-odt.el: Cannot open load file: table which is odd, since I have a (require 'table) in my edit file. Did anybody sucessfully compile the latest org version under Xemacs 21.5.X? Uwe Brauer
[O] Problem with org-insert-heading on multi-line items?
Hi folks, I'm using Org 8.0.3 and Emacs 24.3.1. I noticed with interest this note in the Org 8.0 release notes: When a list item has a checkbox, inserting a new item uses a checkbox too. I'm finding, however, that Org will in many cases insert a new checkbox even if the current item has none. Specifically, invoking org-insert-heading on the second or subsequent lines of a multi-line item will create a new checkbox item every time, whether the current item has a checkbox or not. To illustrate: 1. org-insert-heading invoked here creates a new plain item 2. org-insert-heading invoked on this second item does the same 3. However, org-insert-heading, invoked on the SECOND line of this creates a following checkbox item: 4. [ ] However, invoking org-insert-heading on the first line of a multi-line item creates new items of the correct type, checkbox or not. So it seems like the first line is determinative. May I ask if anybody else is seeing this behavior? Is it as designed? Regards, Tom Davey -- Tom Davey t...@tomdavey.com New York NY USA
[O] Archive scheduled (done) items to date-tree wrt scheduled date - Was: Was: Re: Can I set achive or refile target to date-tree?
Hi. I found the org-archive-subtree-defadvice.el quite useful, but I'd like to be able to archive DONE items not to today's date in a date-tree archive file, but instead to their scheduled date. Thus, it reconstructs a journal of done things, and not a journal of my archiving activity. Anyone with a suggestion ? Thanks in advance. Best regards, Osamu OKANO okano.os...@gmail.com writes: Hi, all. I wrote the defadvice of org-archive-subtree so that I can archive in a date-tree. Please (setq org-archive-location %s_archive::date-tree), then you can archive in a date-tree. http://gist.github.com/370843 Regards. -- Olivier BERGER (OpenPGP: 4096R/7C5BB6A5) http://www.olivierberger.com/weblog/
Re: [O] Minor problems with dvipng latex image preview
Nick Dokos ndo...@gmail.com writes: Nicolas Goaziou n.goaz...@gmail.com writes: Anyway, in a nutshell, your proposal is to: - add a custom variable, e.g., `org-latex-dvi-process-options' (which library should it belong to?) Unless it would make sense to toss the whole dvipng thing overboard and just keep imagemagick. I'm not sure there is a really good reason to drop it. Is it inferior in some way? Also, imagemagick is not optimal either. Since it uses `org-latex-pdf-process', pdflatex is called three times by default, which is unnecessary for a short snippet. So, both dvipng and imagemagick should have a variable to set the program to call, along with its arguments. - modify `org-latex-listings' docstring (in particular, add third elements and new custom variable) I'm not sure any more that it can all be explained clearly in the docstring (at least I've been trying different mental gyrations and I have not come up with anything satisfactory). So maybe the thing to do is add a page to worg and a pointer to it in the docstring. If that's acceptable, I volunteer to write the worg page (at least the initial version). A worg page can't hurt, but a URL in the docstring is not very handy either. It also defeats the self-documenting part of Emacs. As a separate issue, I proposed some debugging aids: - add a custom variable, e.g., `org-latex-dvi-process-debug', which, when non-nil asks to leave produced tex file. ... and a call-process-log function that logs the command in *Messages* before executing it with call-process (or something more or less equivalent). It would be used wherever call-process is used now. I would actually propose that the debug variable inhibit the deletion of intermediate files everywhere, not just in latex preview. Some parts of Org already have their own debug variable (see `org-export-async-debug'). A meta debug variable would not be optimal, would it? Regards, -- Nicolas Goaziou
Re: [O] [PATCH][ox-koma-letter]: sender, email and cleanup
Rasmus ras...@gmx.us writes:
4. Sets defcustom org-koma-letter-signature nil since that
corresponds to default scrlttr2 behavior anyway (p. 183 in the
manual).
Re 4.: I'd like to do something similar to
org-koma-letter-subject-format. But I'm not sure how, at the moment
(perhaps make t the default and associate it with the current default
list).
This patch makes the subject option easier although still relying on
a list for multiple options (see the description in the patch). The
default is t corresponding to do nothing but print komavar subject.
I haven't found any bugs but please test it (along with other patches)
if time permits.
A potential problem is that subject default to the file name and can
only be disabled with the option subject:nil. The file name to title
convention is bad in ox-latex.el and I think it's if anything worse
here. I'd like to make it nil by default. What do you guys think?
–Rasmus
PS: Perhaps it would it be beneficial to make some test-letter
displaying the different scenarios in which we use ox-koma-letter? To
make sure that stuff doesn't get broken.
--
May the Force be with you
From 880f99622a4513520d1dd4e110428f18453a3af1 Mon Sep 17 00:00:00 2001
From: rasmus.pank rasmus.p...@gmail.com
Date: Sat, 25 May 2013 20:49:57 +0200
Subject: [PATCH 5/5] Only print subject options when necessary
* ox-koma-letter.el (org-koma-letter-subject-format): default is now t
* ox-koma-letter.el (org-koma-letter-template): better subject handling.
If =#+OPTIONS: subject:(x,y)= then =\KOMAoption{subject}{x, y}=. If
=subject:x= then =\KOMAoption{subject}{x}=.
If =subject:t= then =\KOMAoption{subject}{...}= is not printed but
\setkomavar{subject}{...} is printed. If =subject:nil= neither are
printed.
---
contrib/lisp/ox-koma-letter.el | 21 +
1 file changed, 9 insertions(+), 12 deletions(-)
diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index 4cb402e..ca20ec7 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -137,7 +137,7 @@ function may be given. Functions must return a string.
:group 'org-export-koma-letter
:type 'string)
-(defcustom org-koma-letter-subject-format '(beforeopening left untitled)
+(defcustom org-koma-letter-subject-format t
Use the title as the subject of the letter. At the time of
writing the following values are allowed:
@@ -162,6 +162,7 @@ English manual of 2012-07-22)
(const titled)
(const untitled)
(const :tag No export nil)
+ (const :tag Default options t)
(string))
:group 'org-export-koma-letter)
@@ -432,20 +433,16 @@ holding export options.
\\begin{document}\n\n
;; Subject
(let* ((with-subject (plist-get info :with-subject))
- (subject-format
- (if (member
- ;; test if subject-format is t
- (cond ((symbolp with-subject) (downcase (symbol-name with-subject)))
- ((stringp with-subject) (downcase with-subject))
- (t nil))
- '(true t))
- org-koma-letter-subject-format
- with-subject))
+ (subject-format (cond ((member with-subject '(true t t)) nil)
+((stringp with-subject) (list with-subject))
+((symbolp with-subject)
+ (list (symbol-name with-subject)))
+(t with-subject)))
(subject (org-export-data (plist-get info :title) info))
- (l (if (stringp subject-format) 1 (length subject-format)))
+ (l (length subject-format))
(y ))
(concat
- (when with-subject
+ (when (and with-subject subject-format)
(concat
\\KOMAoption{subject}{
(apply 'format
--
1.8.2.3
Re: [O] Archive scheduled (done) items to date-tree wrt scheduled date
Hi Olivier, org-mode users and -developoers, * Olivier Berger ober...@ouvaton.org [25. May. 2013]: Olivier Berger ober...@ouvaton.org writes: I found the org-archive-subtree-defadvice.el quite useful, but I'd like to be able to archive DONE items not to today's date in a date-tree archive file, but instead to their scheduled date. Thus, it reconstructs a journal of done things, and not a journal of my archiving activity. Anyone with a suggestion ? Responding to myself : there's now a ::datetree/ option for org-archive-location which renders the org-archive-subtree-defadvice.el hack useless. Is it possible to refile to a date tree? This would be very helpful. Ciao; Gregor
Re: [O] [PATCH] ox-koma-letter.el: Reintroduce variables removed in commit 832c6fd with proper defaults
Hi Robert, what I meant is, if #+AUTHOR defaults to (user-full-name), could the \setkomavar commands be placed /before/ \LoadLetterOption in the TeX file, and after \LoadLetterOptions if #+AUTHOR is set in the .org file? So you'd still get only one set of \setkomavar in the TeX file, but get a (for me) more useful order of #+AUTHOR != (user-full-name) #+LCO #+AUTHOR == (user-full-name) I see. It could be done but it could be kind of inconvenient, I guess, since currently #+AUTHOR and the default org-koma-letter-author share the same variable name during export. You can always disable it with empty values, although a bit of a hassle (e.g. #+AUTHOR:\n). If my memory serves me correctly Viktor decided the order of LCO values versus file values carefully so he'll have a better idea about this. That being said, I can think of two ways to do it. 1. use something like `org-koma-letter--prepare-special-contents-as-macro' and make an ordering dependent on a list like with org-koma-letter-special-tags-after-closing. 2. Test whether a particular value is equal to the default. But it seems like something that could easily go wrong. . . –Rasmus -- Hvor meget poesi tror De kommer ud af et glas isvand?
Re: [O] [OT] Gnus mail tutorial?
Jacek Generowicz jacek.generow...@cern.ch writes: Marcin Borkowski writes: I'm thinking about using Emacs as my email client, and I'm considering using Gnus for that. If it is Emacs rather than Gnus itself that attracts you, then you might consider notmuch or mu4e. Both have a Xapian-based core, and include an Emacs interface. +1. I used Gnus with an IMAP account for a while, but found that (in addition to being intimidating and complicated) it was annoyingly slow. I did write a brief tutorial about getting it set up, which you may or may not find useful; it's at [1]. I still use Gnus to read news (e.g., this list, via Gmane), which is much simpler to set up, and pretty handy. After abandoning Gnus for mail, but wishing to remain in Emacs, I tried nmh with MH-E as a front end. I liked MH-E well enough, but the big problem was that I couldn't find any program to sync mail in both directions from MH directories, and I want a local copy of my mail on multiple machines which reflects the state on the IMAP server. So, long story short, I have now switched to using offlineimap to sync over IMAP with a Maildir. This keeps my mail locally available but also in sync across multiple machines. I read this Maildir in mutt, not Gnus, because I read nasty things on the Internet about how Gnus' Maildir implementation really stinks (e.g., it uses its own tagging system instead of the standard Maildir flags, and it eats up inodes on your filesystem like crazy). I use notmuch to index it, and notmuch-mode in Emacs to search it. I have my mutt editor set to emacsclient. It ain't perfect, by any means (and if anyone has suggestions on a better setup, I'd love to hear them), but it works for me. [1] http://whereofwecannotspeak.wordpress.com/2009/07/15/getting-gnus-to-read-mail-over-imap/ -- Best, Richard
Re: [O] [OT] Gnus mail tutorial?
On Sat, May 25, 2013 at 03:29:03PM -0700, Richard Lawrence wrote: So, long story short, I have now switched to using offlineimap to sync over IMAP with a Maildir. This keeps my mail locally available but also in sync across multiple machines. I read this Maildir in mutt, not Gnus, because I read nasty things on the Internet about how Gnus' Maildir implementation really stinks (e.g., it uses its own tagging system instead of the standard Maildir flags, and it eats up inodes on your filesystem like crazy). I use notmuch to index it, and notmuch-mode in Emacs to search it. I have my mutt editor set to emacsclient. I use this mutt fork instead of mutt. https://github.com/karelzak/mutt-kz -- Suvayu Open source is the future. It sets us free.
Re: [O] Build-System: Why not compile contrib
Hi Stefan, On Sat, May 25, 2013 at 04:19:27PM +0200, Stefan Nobis wrote: Hi. I'm using the maint branch of org-mode and lately I discovered that the files beneath contrib are not compiled and there seems to be no easy way (e.g. via local.mk) to enable compilation of contrib. Is this on purpose and if yes: why? http://orgmode.org/worg/dev/org-build-system.html#sec-4-1-2 Hope this helps, -- Suvayu Open source is the future. It sets us free.
[O] LaTeX minted --shell-escape error after updating to 8.0.3
Hi,
I updated org-mode to 8.0.3 (release_8.0.3-156-g847637). I got the
following error while using the LaTeX export, before the update all
was well and the PDF file was produced fine.
Process completed with errors: [LaTeX error] [package error]
*Org PDF LaTeX Output* shows:
...
...
Package ifplatform Warning:
shell escape is disabled, so I can only detect \ifwindows.
))
! Package minted Error: You must invoke LaTeX with the -shell-escape flag.
See the minted package documentation for explanation.
Type H return for immediate help.
...
l.21 \usemintedstyle
{autumn}
! Package minted Error: You must have `pygmentize' installed to use this packag
e.
See the minted package documentation for explanation.
Type H return for immediate help.
...
...
I have not changed any settings in my .emacs file (i.e.: (setq
org-export-latex-listings 'minted) is unchanged) and I never faced any
problems related to the `--shell-escape' before the update. pygmentize
is present in /usr/bin/ and it too worked perfectly before the update.
Any help is appreciated.
Thank you,
Sincerely,
Senthil
Re: [O] GFDL
Bastien b...@gnu.org writes: Sebastien Vauban sva-n...@mygooglest.com writes: FMI, why is GNU GPL not applicable to the manual? Because the manual is part of GNU Emacs, which is part of the GNU project, and every project in the GNU project is required to publish manuals in GNU FDL only. Dual licensing is not an option here. Wow, I didn't realise the FSF policy was *that* restrictive. Publishing the manual under both FDL and GPL should satisfy the FSF's legitimate requirements for their work, so I don't know how they justify refusing a manual that happens to also be published under some non-FDL license. Do you have a reference from some FSF official for that restriction? There are many discussions about this... a can of (dead) worms. Agreed, thank you. -- \“Every sentence I utter must be understood not as an | `\ affirmation, but as a question.” —Niels Bohr | _o__) | Ben Finney
Re: [O] org-export, table.el complex tables, latex html
On 25.5.2013, at 22:09, Nicolas Goaziou n.goaz...@gmail.com wrote: Uwe Brauer o...@mat.ucm.es writes: What's about orgtbl-to-latex does this work for you also? It doesn't seem to. orgtbl-to-* does not support table.el tables. - Carsten Regards, -- Nicolas Goaziou
