[O] direct link to mails in gmail
Hi,
I just figured out some kind of very interesting possibility.
All the personal data and security feelings aside, I use a gmail account
since I share it between many different computers.
In my org-files, I would sometimes like to link to a particular mail
e.g., for reference purpose.
Today I noticed that each email in my google mail account has a unique
and fixed URL.
Thus, I gave it a try
1. Open your gmail account (log-in)
2. Open the mail you like to refer too.
3. Copy the URL
4. Add the URL as a link (C-c C-l) to your org-file
After that, clicking on the link will open the mail directly in your
standard webbrowser. If you logged out from google mail in between, you
are ask to log-in first, after that select the link again.
But it is getting even better. You are not only able to link to
particular mails within org-mode, but also to google mail labels
(folders) or search results.
To make it even more org-mode friendly one can set-up org-capture in
your webbrowser [1].
I added the following to the org-capture-templates list
("g" "Gmail-link" entry (file+headline "~/org/work.org" "Gmail-links") "%A")
Thus, pressing the assigned button in your browser and emacs will ask
you what kind of link you want to add to your file. Press g for gmail
and enter the description for the link (this could be done
automatically, but I find it to long and not helpful). You will find the
link in your capture buffer in emacs for further processing
I really like it and I hope others find this useful too.
Not sure about the safety issue to link to URLs within your gmail
account. Maybe others can comment on this.
All the best
Totti
[1] http://orgmode.org/worg/org-contrib/org-protocol.html
Re: [O] Export an org file from the command line in the background
Viktor Rosenfeld wrote: > ... > One more question, it doesn't matter if I put the code in the > file that is loaded via -l or in the --eval block, correct? I've > included the code in the my org file, so I can tangle it. I find it > better to have all the Emacs code in one location. > Correct. Which is preferable is very much a matter of usage patterns and taste. > Here's what I came up with: > > (add-to-list 'load-path (expand-file-name "~/unix/src/org-mode/lisp")) > (add-to-list 'load-path (expand-file-name > "~/unix/src/org-mode/contrib/lisp")) > (require 'org) > (require 'ob-sh) > (require 'ansi-color) > (let ((ansi-color-for-comint-mode nil) > (org-confirm-babel-evaluate nil) > (org-use-sub-superscripts nil)) > (find-file "~/org/projects/macports/macports.org") > (org-with-point-at > (org-id-find "83583083-47B7-44DF-8474-1C6D03491C97" 'marker) > (org-babel-execute-subtree)) > (org-export-as-html t) > (kill-buffer)) You don't need the kill-buffer if emacs is just going to exit. But it doesn't hurt. Nick
Re: [O] Export an org file from the command line in the background
Hi Nick, Nick Dokos wrote: > The usual method is to run a separate emacs in batch mode: that will avoid > any conflicts > with the running instance. But batch implies -q, so you will have to provide > a minimal .emacs > file that sets up enough structure to enable you to do what you want: > > emacs --batch -l ~/minimal.emacs \ >--eval '(let ((org-confirm-babel-evaluate nil)) > (find-file "macports.org") > (org-export-as-html 3))' > > should do it. Thanks for your help. I got it running using a similar setup. One more question, it doesn't matter if I put the code in the file that is loaded via -l or in the --eval block, correct? I've included the code in the my org file, so I can tangle it. I find it better to have all the Emacs code in one location. Here's what I came up with: (add-to-list 'load-path (expand-file-name "~/unix/src/org-mode/lisp")) (add-to-list 'load-path (expand-file-name "~/unix/src/org-mode/contrib/lisp")) (require 'org) (require 'ob-sh) (require 'ansi-color) (let ((ansi-color-for-comint-mode nil) (org-confirm-babel-evaluate nil) (org-use-sub-superscripts nil)) (find-file "~/org/projects/macports/macports.org") (org-with-point-at (org-id-find "83583083-47B7-44DF-8474-1C6D03491C97" 'marker) (org-babel-execute-subtree)) (org-export-as-html t) (kill-buffer)) Thanks again, Viktor
[O] Code block evaluation export bug ? (was: Re: Export an org file from the command line in the background)
While testing my response to Viktor's question, I ran into a problem.
I used a test file that is slightly modified from a previous post of Tom Dye's:
--8<---cut here---start->8---
* R tables
#+TBLNAME: tbl-1
| column1 | column2 |
|-+-|
| 45 | 34 |
| 77 | 56 |
#+tblname: tbl-2
| col1 | col2 |
|--+--|
| a| b|
| c| d|
#+tblname: tbl-3
| c1 | c2 |
|+|
| A | B |
| C | D |
#+BEGIN_SRC R :var x=tbl-1 :var y=tbl-2 :var z=tbl-3 :colnames yes :exports
both :results value
z
#+END_SRC
--8<---cut here---end--->8---
Evaluating the code block correctly produces the result
,
|
| #+results:
| | c1 | c2 |
| |+|
| | A | B |
| | C | D |
`
but exporting (to ascii, PDF, HTML or ODT) chops off the first row of the
result. For example, here
is the ascii:
,
|
| c1 c2
| +
| CD
`
HTML produces:
,
|
| c1 c2
| 1 C D
|
`
Latex:
,
| \begin{center}
| \begin{tabular}{ll}
| c1 & c2 \\
| \hline
| C & D \\
| \end{tabular}
| \end{center}
`
ODT:
,
|
|
|
|
|
| c1
|
| c2
|
|
|
|
|
| C
|
| D
|
|
|
|
|
`
Versions:
GNU Emacs 24.0.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0) of
2011-09-13
Org-mode version 7.7 (release_7.7.396.gfaaa)
Nick
Re: [O] Export an org file from the command line in the background
Viktor Rosenfeld wrote:
> Hi,
>
> Jambunathan K wrote:
>
> >
> > C-h v org-export-run-in-background
>
> This only works for org-export, but not for org-export-as-XXX.
>
> Additionally, it appears that setting org-confirm-babel-evaluate locally
> does not have an effect on background exports. Even setting it globally
> in a running Emacs instance won't work; the command has to be in a file
> that is loaded during Emacs startup.
>
> The help contains the following text which I don't understand:
>
> This variable is safe as a file local variable if its value
> satisfies the predicate which is byte-compiled expression.
>
> Cheers,
> Viktor
>
> >
> > > Hi,
> > >
> > > is it possible to export an org file from the command line, so that a
> > > currently running Emacs instance is not disturbed? I want to export the
> > > attached org file and run the included source blocks, so I have an
> > > activity report in the end. I use the shell script pasted below, but
> > > there are two problems:
> > >
> > > - my Emacs instance is blocked during the execution of the shell
> > > scripts contained in the file
> > > - the script globally sets org-confirm-babel-evaluate to nil for my
> > > Emacs instance
> > >
> > > The second problem could possibly be solved with a local file variable.
> > > But the first problem remains. If I use emacs instead of emacsclient, it
> > > complains about a running Emacs instance.
> > >
> > > #!/bin/sh
> > >
> > > emacsclient -c \
> > > --eval "(progn
> > > (find-file \"macports.org\"))
> > > (setq org-confirm-babel-evaluate nil)
> > > (org-export-as-html 3)
> > > (kill-buffer)
> > > (delete-frame))"
> > >
> > > I'm using Org-Mode 7.7.
> > >
The usual method is to run a separate emacs in batch mode: that will avoid any
conflicts
with the running instance. But batch implies -q, so you will have to provide a
minimal .emacs
file that sets up enough structure to enable you to do what you want:
emacs --batch -l ~/minimal.emacs \
--eval '(let ((org-confirm-babel-evaluate nil))
(find-file "macports.org")
(org-export-as-html 3))'
should do it.
minimal.emacs would just load org - modulo path differences, something like:
--8<---cut here---start->8---
;;; -*- mode: emacs-lisp -*-
;;; constant part
(add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/lisp"))
(add-to-list 'load-path (expand-file-name
"~/src/emacs/org/org-mode/contrib/lisp"))
(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
(require 'org-install)
--8<---cut here---end--->8---
Also note the let bind of org-confirm-babel-evaluate: that would alleviate the
second problem you mentioned above in the emacsclient case (and although it's
irrelevant in the emacs case, I still prefer the let bind over the explicit
setq).
HTH,
Nick
Re: [O] Export an org file from the command line in the background
Hi, Jambunathan K wrote: > > C-h v org-export-run-in-background This only works for org-export, but not for org-export-as-XXX. Additionally, it appears that setting org-confirm-babel-evaluate locally does not have an effect on background exports. Even setting it globally in a running Emacs instance won't work; the command has to be in a file that is loaded during Emacs startup. The help contains the following text which I don't understand: This variable is safe as a file local variable if its value satisfies the predicate which is byte-compiled expression. Cheers, Viktor > > > Hi, > > > > is it possible to export an org file from the command line, so that a > > currently running Emacs instance is not disturbed? I want to export the > > attached org file and run the included source blocks, so I have an > > activity report in the end. I use the shell script pasted below, but > > there are two problems: > > > > - my Emacs instance is blocked during the execution of the shell > > scripts contained in the file > > - the script globally sets org-confirm-babel-evaluate to nil for my > > Emacs instance > > > > The second problem could possibly be solved with a local file variable. > > But the first problem remains. If I use emacs instead of emacsclient, it > > complains about a running Emacs instance. > > > > #!/bin/sh > > > > emacsclient -c \ > > --eval "(progn > > (find-file \"macports.org\")) > > (setq org-confirm-babel-evaluate nil) > > (org-export-as-html 3) > > (kill-buffer) > > (delete-frame))" > > > > I'm using Org-Mode 7.7. > > > > Cheers, > > Viktor > > > > -- >
Re: [O] Cdlatex questions
Carsten Dominik writes: > Hi Rasmus, > > you need to set these variables before cdlatex.el has been loaded, or you need > run (cdlatex-reset-mode) after you have changed them. THis is not documented > well, > unfortunately. Thanks Carsten. For the reference I use the following snip now which and it works as I want it to work. #+begin_src emacs-lisp (add-to-list 'cdlatex-math-modify-alist '(98 "\\boldsymbol" "\\textbf" t nil nil)) (add-to-list 'cdlatex-math-modify-alist '(115 "\\mathbb" nil t nil nil)) (org-defkey org-cdlatex-mode-map "¨" 'cdlatex-math-symbol) (setq cdlatex-math-symbol-prefix 168) ;;(cdlatex-reset-mode) (require 'cdlatex) #+end_src –Rasmus -- Sent from my Emacs
Re: [O] outline-demote incorrectly demotes leaf nodes
Carsten, Thank you for the very clear explanation. I like this option that you suggested: (add-hook 'org-mode-hook (lambda () (define-key org-mode-map [(control ?<)] 'org-promote-subtree) (define-key org-mode-map [(control ?>)] 'org-demote-subtree))) It makes outline mode adapt to the new age (org mode). -- -Sanjoy `Until lions have their historians, tales of the hunt shall always glorify the hunters.' --African Proverb
Re: [O] org-odt: specifying fonts
Hi, Mehul,
It's not that I would be opposed to a fonts option, of course, but I
don't see it as a priority or even necessary. As long as org-odt
handles the document structure and semantics right, and allows
attaching an external stylesheet, I think it's done its job.
There are other developments I'm more keen on, like a finalized set of
documented header options for images (those often need to be set on a
per-image basis), or the table styles Jambunathan's been experimenting
with (OpenOffice, eat your heart out!), or simply the definitive
integration of the odt exporter into core Org.
On 10/18/11 11:15 PM, Mehul Sanghvi wrote:
As for fonts, like styles, it
would be easier, simpler and more elegant
to be able to do that without having to edit styles.odt every time.
This is not specific to org-odt. It should be,
at least I think so for now, to do this with any exporting backend.
Some would say tinkering with fonts is a distraction from writing that
having Your Life In Plain Text allows you to get away from. And the
consistent use of styles and templates is anyway good word-processing
practice.
But sure, this is possible in other backends. For html export (which I
know better than latex), one can simply include a header like:
#+STYLE: * { font-family: Gentium; }
to make every element use the Gentium font if available. If I need
more than 2-3 STYLE headers to get a job done, though, I find it
easier, simpler and more elegant to link to an external stylesheet.
HTML comes with the breathtaking power and simplicity of CSS styling;
LaTeX comes with breathtaking power and ... well, at least it's in
plain text that Org can pass on to the relevant backend. ODT is a
slightly different story. Its styles are in XML that was not really
meant to be hand-edited.
If you send me a styles.odt, and I do not like the fonts you are
using, it becomes cumbersome to be editing the styles.odt
for each font and making sure to change it in all possible places
until I settle on a proper font I want to use.
If I could instead specify the font in org file itself, it would be a
matter of changing the header and re-generating the file.
You'd still need to do the cumbersome work of making sure to change it
in all possible places, though. Changing the Default paragraph style
will typically change e.g. the linked Text Body style, too , but not
the headings (they're linked with Heading). So at a minimum, you'd
need options to modify both. And once fonts can be specified, users
will want sizes, weights, colors, borders, etc. Sure, there could be
an extensive options vocab a la:
#+ODT_STYLE: "Default" :type para :font "Gentium" :size 12pt
#+ODT_STYLE: "Heading" :type para :font "Arial" :size 16pt :weight
bold :color blue :borders ...etc. etc. ...
But is it needed? While Latex, HTML and DocBook users should never be
required to sully their hands with a GUI, when we use ODT we can
reasonably be expected to open up an office application now and again
to modify our templates.
Okay, #+END_RANT...
Yours,
Christian
Re: [O] org-odt: specifying fonts
On 10/19/11 7:54 PM, Jambunathan K wrote: #+ODT_STYLES_FILE: "/path/to/styles.xml" Perfect. Thanks for the quick response! Yours, Christian
Re: [O] org-odt: specifying fonts
On Wed, Oct 19, 2011 at 13:54, Jambunathan K wrote:
>
>> I agree with Mehul it would be great to have an option to specify a
>> styles file on a per-file basis. Something like:
>>
>> #+ODT_STYLE: ~/org/odt-templates/cv.odt
>
> I have gone with `#+ODT_STYLES_FILE: '[1]. Refer the docstring below for a
> sample setting.
>
> ,[ C-h v org-export-odt-styles-file RET ]
> | org-export-odt-styles-file is a variable defined in `org-odt.el'.
> | Its value is nil
> |
> | Documentation:
> | Default styles file for use with ODT export.
> | Valid values are one of:
> | 1. nil
> | 2. path to a styles.xml file
> | 3. path to a *.odt or a *.ott file
> | 4. list of the form (ODT-OR-OTT-FILE (FILE-MEMBER-1 FILE-MEMBER-2
> | ...))
> |
> | [snip]
> |
> | Use "#+ODT_STYLES_FILE: ..." directive to set this variable on
> | a per-file basis. For example,
> |
> | #+ODT_STYLES_FILE: "/path/to/styles.xml" or
> | #+ODT_STYLES_FILE: ("/path/to/file.ott" ("styles.xml" "image/hdr.png")).
> |
> | You can customize this variable.
> `
>
> Hope it is OK.
>
> Footnotes:
> [1] The name of the option is same as the upcased custom variable name
> with `org-export-' prefix stripped. The same convention can be used for
> any "future" per-file odt settings.
> --
>
Awesome !! Thanks Jambunathan
--
Mehul N. Sanghvi
email: mehul.sang...@gmail.com
Re: [O] [babel] Verbatim output from SQL command
"Sebastien Vauban" writes: > Hi Eric, > > Eric Schulte wrote: >>> Babel seems to interpret every *leading space* as *one empty column*. >>> Normal, feature, bug? >>> >>> Is there some workaround to this? I thought stating "scalar" would really >>> completely override any interpretation... >> >> I've just pushed up a fix which should resolve this issue. > > It does better things, but at least at the wrong place. > oh, I forgot to insert into a temporary buffer. This should now be fixed. Thanks -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] org-odt: specifying fonts
> I agree with Mehul it would be great to have an option to specify a
> styles file on a per-file basis. Something like:
>
>#+ODT_STYLE: ~/org/odt-templates/cv.odt
I have gone with `#+ODT_STYLES_FILE: '[1]. Refer the docstring below for a
sample setting.
,[ C-h v org-export-odt-styles-file RET ]
| org-export-odt-styles-file is a variable defined in `org-odt.el'.
| Its value is nil
|
| Documentation:
| Default styles file for use with ODT export.
| Valid values are one of:
| 1. nil
| 2. path to a styles.xml file
| 3. path to a *.odt or a *.ott file
| 4. list of the form (ODT-OR-OTT-FILE (FILE-MEMBER-1 FILE-MEMBER-2
| ...))
|
| [snip]
|
| Use "#+ODT_STYLES_FILE: ..." directive to set this variable on
| a per-file basis. For example,
|
| #+ODT_STYLES_FILE: "/path/to/styles.xml" or
| #+ODT_STYLES_FILE: ("/path/to/file.ott" ("styles.xml" "image/hdr.png")).
|
| You can customize this variable.
`
Hope it is OK.
Footnotes:
[1] The name of the option is same as the upcased custom variable name
with `org-export-' prefix stripped. The same convention can be used for
any "future" per-file odt settings.
--
[O] Exporting selected tasks (maybe from agenda view) including their body.
Is there a possibility to export tasks including their body (text, maybe logbook etc.) from the agenda view? What I would like to do is the following: I have Tasks with a certain todo state (e.g. WAITING). I can view all these tasks in an agenda view. Now I need to leave my computer and want to print out every task showing up in the agenda view (e.g. every task with a WAITING todo state) including the bodies of the tasks (the whole text that shows up in the org file, maybe without logbook drawers). It should work like exporting to HTML (because the latex formulas should be compiled) but picking only some tasks of multiple org files. Does such an export function exist? If not, how could I achieve this? Thanks, Dominik
Re: [O] [babel] Verbatim output from SQL command
Hi Viktor and Nick,
Nick Dokos wrote:
> Viktor Rosenfeld wrote:
>> Sebastien Vauban wrote:
>>
>> > #+BABEL: :engine msosql :cmdline -S -U -P -d
>> > -n -w 700
>>
>> Where is the :engine directive documented?
>
> The only place I know of is lisp/ob-sql.el - there is support for the
> following engines currently:
>
>
> ,
> | ...
> | ('msosql (format "osql %s -s \"\t\" -i %s -o %s"
> | (or cmdline "")
> | (org-babel-process-file-name in-file)
> | (org-babel-process-file-name
> out-file)))
> | ('mysql (format "mysql %s < %s > %s"
> | (or cmdline "")
> | (org-babel-process-file-name in-file)
> | (org-babel-process-file-name out-file)))
> | ('postgresql (format
> | "psql -A -P footer=off -F \"\t\" -f %s -o %s
> %s"
> | (org-babel-process-file-name in-file)
> | (org-babel-process-file-name out-file)
> | (or cmdline "")))
> | (t (error "no support for the %s sql engine" engine)
> | ...
> `
Nothing to add. The `engine' directive is SQL-specific.
Note that I have in mind to add such an `engine' directive to Ledger as well:
being able to let the transactions be processed by `ledger', `hledger' or
`beancount' -- the ones I know of, and which are mostly compatible between
each other.
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [babel] Verbatim output from SQL command
Cool, thanks!
Nick Dokos wrote:
> Viktor Rosenfeld wrote:
>
> > Hi,
> >
> > Sebastien Vauban wrote:
> >
> > > #+BABEL: :engine msosql :cmdline -S -U -P -d
> > > -n -w 700
> >
> > Where is the :engine directive documented?
> >
>
> The only place I know of is lisp/ob-sql.el - there is support for the
> following engines currently:
>
>
> ,
> | ...
> | ('msosql (format "osql %s -s \"\t\" -i %s -o %s"
> | (or cmdline "")
> | (org-babel-process-file-name in-file)
> | (org-babel-process-file-name
> out-file)))
> | ('mysql (format "mysql %s < %s > %s"
> | (or cmdline "")
> | (org-babel-process-file-name in-file)
> | (org-babel-process-file-name out-file)))
> | ('postgresql (format
> | "psql -A -P footer=off -F \"\t\" -f %s -o %s
> %s"
> | (org-babel-process-file-name in-file)
> | (org-babel-process-file-name out-file)
> | (or cmdline "")))
> | (t (error "no support for the %s sql engine" engine)
> | ...
> `
>
> Nick
>
>
Re: [O] org-list-indent-offset only works partially
Hi Nicolas Thanks for the explanations, it helps me to get the right perspective to all the various possibilities. And the reread of the manual about Plain lists reminded me of org-M-RET-may-split-line that I will configure now. Michael
Re: [O] [babel] Verbatim output from SQL command
Viktor Rosenfeld wrote:
> Hi,
>
> Sebastien Vauban wrote:
>
> > #+BABEL: :engine msosql :cmdline -S -U -P -d
> > -n -w 700
>
> Where is the :engine directive documented?
>
The only place I know of is lisp/ob-sql.el - there is support for the following
engines currently:
,
| ...
| ('msosql (format "osql %s -s \"\t\" -i %s -o %s"
| (or cmdline "")
| (org-babel-process-file-name in-file)
| (org-babel-process-file-name out-file)))
| ('mysql (format "mysql %s < %s > %s"
| (or cmdline "")
| (org-babel-process-file-name in-file)
| (org-babel-process-file-name out-file)))
| ('postgresql (format
| "psql -A -P footer=off -F \"\t\" -f %s -o %s
%s"
| (org-babel-process-file-name in-file)
| (org-babel-process-file-name out-file)
| (or cmdline "")))
| (t (error "no support for the %s sql engine" engine)
| ...
`
Nick
Re: [O] Prompt for time when clocking in?
Nathan Neff writes: > Is there a way to pull up a date/time prompt when clocking in to a task? > > Sometimes, I started a task 15 minutes ago, and have to go through the > following > steps: > > 1) clock in on the task, > 2) Go to the CLOCK section for that header and press tab to open it > 3) Fix the clock-in time > > If it's not built in, does anyone have any slick functions that would > accomplish > the same thing? :-) > > Thanks, > --Nate For editing clock times I use the agenda C-c a a v c and then visit the lines I want to edit from the agenda with RET. HTH, Bernt
Re: [O] [babel] Verbatim output from SQL command
Hi, Sebastien Vauban wrote: > #+BABEL: :engine msosql :cmdline -S -U -P -d > -n -w 700 Where is the :engine directive documented? Cheers, Viktor
Re: [O] Export an org file from the command line in the background
C-h v org-export-run-in-background > Hi, > > is it possible to export an org file from the command line, so that a > currently running Emacs instance is not disturbed? I want to export the > attached org file and run the included source blocks, so I have an > activity report in the end. I use the shell script pasted below, but > there are two problems: > > - my Emacs instance is blocked during the execution of the shell > scripts contained in the file > - the script globally sets org-confirm-babel-evaluate to nil for my > Emacs instance > > The second problem could possibly be solved with a local file variable. > But the first problem remains. If I use emacs instead of emacsclient, it > complains about a running Emacs instance. > > #!/bin/sh > > emacsclient -c \ > --eval "(progn > (find-file \"macports.org\")) > (setq org-confirm-babel-evaluate nil) > (org-export-as-html 3) > (kill-buffer) > (delete-frame))" > > I'm using Org-Mode 7.7. > > Cheers, > Viktor > --
[O] Export an org file from the command line in the background
Hi,
is it possible to export an org file from the command line, so that a
currently running Emacs instance is not disturbed? I want to export the
attached org file and run the included source blocks, so I have an
activity report in the end. I use the shell script pasted below, but
there are two problems:
- my Emacs instance is blocked during the execution of the shell
scripts contained in the file
- the script globally sets org-confirm-babel-evaluate to nil for my
Emacs instance
The second problem could possibly be solved with a local file variable.
But the first problem remains. If I use emacs instead of emacsclient, it
complains about a running Emacs instance.
#!/bin/sh
emacsclient -c \
--eval "(progn
(find-file \"macports.org\"))
(setq org-confirm-babel-evaluate nil)
(org-export-as-html 3)
(kill-buffer)
(delete-frame))"
I'm using Org-Mode 7.7.
Cheers,
Viktor
#+TITLE: MacPorts Update Report
* Helper functions
:noexport:
** Set up =$PATH= environment
Set up =$PATH=:
#+begin_src sh :session port-update :results silent
PATH=$PATH:/opt/local/bin
#+end_src
** Table Header for the list of outdated ports
#+begin_src sh :session port-update :results silent
print_outdated_header() {
echo \|Port\|Installed\|Available\|
echo "|--|"
}
#+end_src
** Format each row of =port outdated= as table entry
#+begin_src sh :session port-update :results silent
format_port_outdated() {
awk '{print "|" $1 "|" $2 "|" $4 "|"}'
}
#+end_src
* Outdated ports
The following ports are outdated:
#+begin_src sh :session port-update :results output raw :exports results
print_outdated_header
port -q outdated | format_port_outdated
#+end_src
The following outdated ports are requested:
#+begin_src sh :session port-update :results output raw :exports results
print_outdated_header
port -q outdated and requested | format_port_outdated
#+end_src
* Update log
#+begin_src sh :session port-update :exports results :results verbatim
for i in 1 2 3 4 5 6 7 8 9 0; do echo "."; done
#+end_src
Re: [O] Problem with org-startup-indented
Notably, the problem disappears if I re-evaluate org-indent.el -- I wonder if the bug may be with the package loading? Also, when the issue is present, turning org-indent-mode off manually fixes it, but also produces an error message: "org-indent-mode: Invalid function: org-with-wide-buffer" --aj
Re: [O] how to do footers
Mehul Sanghvi writes: > I know that Org can do foot notes using fn:xxx but what I wanted to do > was put a > footer to every page that is created. It would be the same thing on each > page. > > How would I do that ? Either I missed it in the manual or it is not > there. You need to create the Footer from within LibreOffice. For applying custom styles with footer images you can see this thread. http://lists.gnu.org/archive/html/emacs-orgmode/2011-03/msg01460.html Note that the odt file in that thread has a header image as opposed to a footer image. --
Re: [O] org-odt: specifying fonts
Jambunathan K writes: >> The font thing was just something coming out from the fact that I do >> not know or understand ODT styles. Something new to learn now :) > > This is how you will change the fonts. > > 1. Export your resume.org to resume.odt (without using any custom >styles) > 2. Open resume.odt in LibreOffice > 3. F11 - This will open the stylist window > 4. In paragraphy styles, look for "Default". Right click this and modify >as below > 5. Change the "Times New Roman" etc etc to "Whatever" > 6. Save the file as resume-style.odt > 7. Now customize-variable org-export-odt-styles-file and point it to >resume-style.odt Forgot the last step 8. Re-exporting any subsequent .org file will pick up the new font as saved in resume-style.odt > You are done. > > --
Re: [O] outline-demote incorrectly demotes leaf nodes
Hi Carsten On 18.10.2011, at 20:03, Sanjoy Mahajan wrote: > I do worry about one point, namely that C-c C-> (outline-demote) should still > work. And it does work in regular outline mode. For example, if I rename my > test file to c.otl and then use C-c C-> on the main heading, all the subtrees > are demoted as I expected. Whereas in org mode the leaf subtree gets a space > instead of a * when it is being demoted. On Wed, Oct 19, 2011 at 09:14, Carsten Dominik wrote: > Another option, if you prefer the C-> and C-< bindings is this: > > (add-hook 'org-mode-hook > (lambda () > (define-key org-mode-map [(control ?<)] 'org-promote-subtree) > (define-key org-mode-map [(control ?>)] 'org-demote-subtree))) My suggestion is something like (define-key org-mode-map [remap outline-promote] 'org-promote-subtree) (define-key org-mode-map [remap outline-demote] 'org-demote-subtree) [...] permanently built into Org mode (not in org-mode-hook) for these and maybe even a few more outline-* bindings to get the incompatible outline-* bindings out of the way from within Org mode. This remap does not affect the bindings in Outline mode and resolves the issue of the OP in Org mode, independent of, to which key any user might have mapped outline-*mote. Michael
Re: [O] how to do footers
On Wed, Oct 19, 2011 at 11:35, John Hendy wrote:
> On Wed, Oct 19, 2011 at 10:27 AM, Mehul Sanghvi
> wrote:
>> I know that Org can do foot notes using fn:xxx but what I wanted to do
>> was put a
>> footer to every page that is created. It would be the same thing on each
>> page.
>>
>> How would I do that ? Either I missed it in the manual or it is not there.
>
> If this for LaTeX, you get into that realm vs. org-specific, in my
> opinion (though some may suggest tailoring the org export innards).
> Check out the following:
> --
> http://texblog.wordpress.com/2007/11/07/headerfooter-in-latex-with-fancyhdr/
> -- http://en.wikibooks.org/wiki/LaTeX/Page_Layout#Customising_with_fancyhdr
>
> Here's an example from a recent paper for work. I have this below my
> #+options lines and before the first headline:
> -
> #+begin_latex
> \pagestyle{fancy}
> \setlength{\headheight}{0pt}
> \setlength{\footskip}{40pt}
> \renewcommand{\headrulewidth}{0pt}
> \fancyhf{}
> \cfoot{\thepage}
> \rfoot{\includegraphics[height=7.4pt]{/path/to/company-logo.jpg} Confidential}
> \newpage
> #+end_latex
> -
>
Actually its going to be for Org -> ODT -> {PDF, DOC, RTF}
> John
>
>>
>>
>>
>>
>> --
>> Mehul N. Sanghvi
>> email: mehul.sang...@gmail.com
>>
>>
>
--
Mehul N. Sanghvi
email: mehul.sang...@gmail.com
Re: [O] org-odt: specifying fonts
Matt Price writes: > I think the problem here, Mehul, is that odt export works with > styles, not fonts. So to do what you want, the exporter would need > to be able to tweak the styles manually(so, I guess, first run some > kind of xml transform on the stylesheet, then apply the stylesheet > itself). If there are hidden inconsistencies in the original > stylesheet, you may end up with difficult-to-diagnose breakage. I'd > definitely suggest just modifying hte stylesheet and saving it > somewhere safe. You don't need to apply any set of xml transform or any such thing for the case at hand. --
Re: [O] how to do footers
On Wed, Oct 19, 2011 at 10:27 AM, Mehul Sanghvi wrote:
> I know that Org can do foot notes using fn:xxx but what I wanted to do
> was put a
> footer to every page that is created. It would be the same thing on each
> page.
>
> How would I do that ? Either I missed it in the manual or it is not there.
If this for LaTeX, you get into that realm vs. org-specific, in my
opinion (though some may suggest tailoring the org export innards).
Check out the following:
-- http://texblog.wordpress.com/2007/11/07/headerfooter-in-latex-with-fancyhdr/
-- http://en.wikibooks.org/wiki/LaTeX/Page_Layout#Customising_with_fancyhdr
Here's an example from a recent paper for work. I have this below my
#+options lines and before the first headline:
-
#+begin_latex
\pagestyle{fancy}
\setlength{\headheight}{0pt}
\setlength{\footskip}{40pt}
\renewcommand{\headrulewidth}{0pt}
\fancyhf{}
\cfoot{\thepage}
\rfoot{\includegraphics[height=7.4pt]{/path/to/company-logo.jpg} Confidential}
\newpage
#+end_latex
-
John
>
>
>
>
> --
> Mehul N. Sanghvi
> email: mehul.sang...@gmail.com
>
>
Re: [O] Prompt for time when clocking in?
John Hendy wrote: > On Wed, Oct 19, 2011 at 9:54 AM, Nathan Neff wrote: > > Is there a way to pull up a date/time prompt when clocking in to a task? > > > > Sometimes, I started a task 15 minutes ago, and have to go through the > > following > > steps: > > > > 1) clock in on the task, > > 2) Go to the CLOCK section for that header and press tab to open it > > 3) Fix the clock-in time > > > > If it's not built in, does anyone have any slick functions that would > > accomplish > > the same thing? :-) > > Check out a thread I started a bit back on this exact topic: > --- http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40498.html > > It wasn't exactly what I expected, the suggestion by Bernt for `M-x > org-resolve-clocks` works reasonably well if you are trying to clock > back-to-back activities. Post back after you read that perhaps? Maybe > you'll find something helpful. > org-clock-in takes an optional start-time argument which is used instead of the current time when non-nil. So I tried (setq ct (current-time)) (setq start-time (cons (car ct) (list (- (cadr ct) 900) (caddr ct and started a clock on a task with ESC ESC : (org-clock-in nil start-time) and it got clocked in 15 minutes before the current time. Now I don't propose this as a good UI :-), but it would require just a small wrapper for it to dtrt. HTH, Nick
Re: [O] org-odt: specifying fonts
> The font thing was just something coming out from the fact that I do > not know or understand ODT styles. Something new to learn now :) This is how you will change the fonts. 1. Export your resume.org to resume.odt (without using any custom styles) 2. Open resume.odt in LibreOffice 3. F11 - This will open the stylist window 4. In paragraphy styles, look for "Default". Right click this and modify as below 5. Change the "Times New Roman" etc etc to "Whatever" 6. Save the file as resume-style.odt 7. Now customize-variable org-export-odt-styles-file and point it to resume-style.odt You are done.
[O] how to do footers
I know that Org can do foot notes using fn:xxx but what I wanted to do was put a footer to every page that is created. It would be the same thing on each page. How would I do that ? Either I missed it in the manual or it is not there. -- Mehul N. Sanghvi email: mehul.sang...@gmail.com
Re: [O] org-odt: specifying fonts
On Wed, Oct 19, 2011 at 10:35, Matt Price wrote: > > > On Tue, Oct 18, 2011 at 5:15 PM, Mehul Sanghvi > wrote: >> >> Christian, >> >> Thanks for the stopgap measure. As for fonts, like styles, it >> would be easier, simpler and more elegant >> to be able to do that without having to edit styles.odt every time. >> This is not specific to org-odt. It should be, >> at least I think so for now, to do this with any exporting backend. >> >> If you send me a styles.odt, and I do not like the fonts you are >> using, it becomes cumbersome to be editing the styles.odt >> for each font and making sure to change it in all possible places >> until I settle on a proper font I want to use. >> >> If I could instead specify the font in org file itself, it would be a >> matter of changing the header and re-generating the file. >> >> The ODT_STYLE is certainly a good enhancement. >> > I think the problem here, Mehul, is that odt export works with styles, not > fonts. So to do what you want, the exporter would need to be able to tweak > the styles manually(so, I guess, first run some kind of xml transform on the > stylesheet, then apply the stylesheet itself). If there are hidden > inconsistencies in the original stylesheet, you may end up with > difficult-to-diagnose breakage. I'd definitely suggest just modifying hte > stylesheet and saving it somewhere safe. > m > > I will most likely end up it that way and using that as my workflow. The font thing was just something coming out from the fact that I do not know or understand ODT styles. Something new to learn now :) Now I just got to figure out the fonts that Latex is using for my resume and re-use those same ones in my style and apply them correctly in the ODT styles. -- Mehul N. Sanghvi email: mehul.sang...@gmail.com
Re: [O] Prompt for time when clocking in?
On Wed, Oct 19, 2011 at 9:54 AM, Nathan Neff wrote: > Is there a way to pull up a date/time prompt when clocking in to a task? > > Sometimes, I started a task 15 minutes ago, and have to go through the > following > steps: > > 1) clock in on the task, > 2) Go to the CLOCK section for that header and press tab to open it > 3) Fix the clock-in time > > If it's not built in, does anyone have any slick functions that would > accomplish > the same thing? :-) Check out a thread I started a bit back on this exact topic: --- http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40498.html It wasn't exactly what I expected, the suggestion by Bernt for `M-x org-resolve-clocks` works reasonably well if you are trying to clock back-to-back activities. Post back after you read that perhaps? Maybe you'll find something helpful. John > > Thanks, > --Nate > >
Re: [O] Problem with org-startup-indented
Andrei Jirnyi writes: >> Unfortunately, I'm not running 23.2. A backtrace produced with >> toggle-debug-on-quit and C-g may be helpful though. Could you provide >> one? > > I'm not familiar with the Emacs debugger, so I'm not sure if I am doing > it right -- please let me know if I should do something else. > If (when in the .org buffer, with cursor at the end) I enter M-x toggle- > demand-on-quit [RET] C-g, I get the following in the *Backtrace* buffer > (I repeated the above procedure three times; the output also contained > some non-ascii characters in the "byte-code" sequence which have been > removed): [...] I forgot to tell you to reload Org uncompiled first, with C-u M-x org-reload. Then use M-x toggle-debug-on-quit. Reproduce the freeze with M-x org-indent-mode. Hit C-g. Finally report the backtrace. Thanks. Regards, -- Nicolas Goaziou
Re: [O] Org, Diffs, and Version Control
> > Dave Abrahams boostpro.com> wrote: > > > > I was wondering what other people do. > > I am using http://www.mayrhofer.eu.org/dvcs-autosync for > automatically committing of changes but without activated XMPP sync > feature (so far). > > The already mentioned «git diff --color-words» helps me a lot when > examining my git history. > > -- > Karl Voit > dvcs-autosync is an interesting project The OPs question IIUC is orthogonal to it. The problem as I see it is that org mode docs are two things: -- they are text mode data (when in emacs mode) -- hierarchical data (when in org-specific mode) Diff unfortunately does not understand the hierarchical view. I tried to see if xmldiff will run And if it did then try pipe the output of org-docbook-export to it. Unfortunately my attempts at getting xmldiff to run did not work
Re: [O] why was makefile changed to produce this?
Rémi Vanicat wrote: > Olaf Meeuwissen writes: > > > Nick Dokos writes: > > > > [...] > > > >> $ dpkg -S makeinfo > >> texinfo: /usr/bin/makeinfo > >> octave3.2-common: /usr/share/octave/3.2.4/m/help/__makeinfo__.m > >> emacs23-common: /usr/share/emacs/23.1/lisp/textmodes/makeinfo.elc > >> texinfo: /usr/share/man/man1/makeinfo.1.gz > > > > This only works for installed packages, though, as it searches the files > > below /var/lib/dpkg/info, IIRC. > > BTW, dpkg forwards that request to dpkg-query. > > > > you might want to use apt-files > > $ apt-file search makeinfo > ~ > emacs23-common: /usr/share/emacs/23.3/lisp/textmodes/makeinfo.elc > emacs23-el: /usr/share/emacs/23.3/lisp/textmodes/makeinfo.el.gz > > [...] > > if updated regularly apt-file's database will contain every files in > every package in debian. > Nice - thanks! Nick
[O] Prompt for time when clocking in?
Is there a way to pull up a date/time prompt when clocking in to a task? Sometimes, I started a task 15 minutes ago, and have to go through the following steps: 1) clock in on the task, 2) Go to the CLOCK section for that header and press tab to open it 3) Fix the clock-in time If it's not built in, does anyone have any slick functions that would accomplish the same thing? :-) Thanks, --Nate
Re: [O] org-odt: specifying fonts
On Tue, Oct 18, 2011 at 5:15 PM, Mehul Sanghvi wrote: > Christian, > > Thanks for the stopgap measure. As for fonts, like styles, it > would be easier, simpler and more elegant > to be able to do that without having to edit styles.odt every time. > This is not specific to org-odt. It should be, > at least I think so for now, to do this with any exporting backend. > > If you send me a styles.odt, and I do not like the fonts you are > using, it becomes cumbersome to be editing the styles.odt > for each font and making sure to change it in all possible places > until I settle on a proper font I want to use. > > If I could instead specify the font in org file itself, it would be a > matter of changing the header and re-generating the file. > > The ODT_STYLE is certainly a good enhancement. > > I think the problem here, Mehul, is that odt export works with styles, not fonts. So to do what you want, the exporter would need to be able to tweak the styles manually(so, I guess, first run some kind of xml transform on the stylesheet, then apply the stylesheet itself). If there are hidden inconsistencies in the original stylesheet, you may end up with difficult-to-diagnose breakage. I'd definitely suggest just modifying hte stylesheet and saving it somewhere safe. m
Re: [O] Problem with org-startup-indented
> Unfortunately, I'm not running 23.2. A backtrace produced with
> toggle-debug-on-quit and C-g may be helpful though. Could you provide
> one?
I'm not familiar with the Emacs debugger, so I'm not sure if I am doing
it right -- please let me know if I should do something else.
If (when in the .org buffer, with cursor at the end) I enter M-x toggle-
demand-on-quit [RET] C-g, I get the following in the *Backtrace* buffer
(I repeated the above procedure three times; the output also contained
some non-ascii characters in the "byte-code" sequence which have been removed):
Debugger entered--Lisp error: (quit)
signal(quit nil)
keyboard-quit()
call-interactively(keyboard-quit nil nil)
recursive-edit()
byte-code("\306 @\307=\203!\310\311\312\"\210\313\311!\211A@)\242
\314=\203!\310\315\312\"\210\316!\210\317 \210\320 !\210\f\203d\321ed
\"V\203Web\210\322\245y\210`db\210\322\245Zy\210`|\210)\323c\210eb\210\324
\325\326 \"\210\327\306!\210\324\330!\210\331\312\324\330!\210\212\332
\210+\331\207" [unread-command-char debugger-args x debugger-buffer
noninteractive debugger-batch-max-lines -1 debug backtrace-debug 4 t
backtrace-frame lambda 5 pop-to-buffer debugger-mode debugger-setup-
buffer count-lines 2 "...\n" message "%s" buffer-string kill-emacs "" nil
recursive-edit middlestart buffer-read-only standard-output] 4)
debug(error (quit))
signal(quit nil)
keyboard-quit()
call-interactively(keyboard-quit nil nil)
recursive-edit()
byte-code("\306 @\307=\203!\310\311\312\"\210\313\311!\211A@)\242
\314=\203!\310\315\312\"\210\316!\210\317 \210\320 !\210\f\203d\321ed
\"V\203Web\210\322\245y\210`db\210\322\245Zy\210`|\210)\323c\210eb\210\324
\325\326 \"\210\327\306!\210\324\330!\210\331\312\324\330!\210\212\332
\210+\331\207" [unread-command-char debugger-args x debugger-buffer
noninteractive debugger-batch-max-lines -1 debug backtrace-debug 4 t
backtrace-frame lambda 5 pop-to-buffer debugger-mode debugger-setup-
buffer count-lines 2 "...\n" message "%s" buffer-string kill-emacs "" nil
recursive-edit middlestart buffer-read-only standard-output] 4)
debug(error (quit))
signal(quit nil)
keyboard-quit()
call-interactively(keyboard-quit nil nil)
Re: [O] why was makefile changed to produce this?
Olaf Meeuwissen writes: > Nick Dokos writes: > [...] >> $ dpkg -S makeinfo >> texinfo: /usr/bin/makeinfo >> octave3.2-common: /usr/share/octave/3.2.4/m/help/__makeinfo__.m >> emacs23-common: /usr/share/emacs/23.1/lisp/textmodes/makeinfo.elc >> texinfo: /usr/share/man/man1/makeinfo.1.gz > > This only works for installed packages, though, as it searches the files > below /var/lib/dpkg/info, IIRC. > BTW, dpkg forwards that request to dpkg-query. > you might want to use apt-files $ apt-file search makeinfo ~ emacs23-common: /usr/share/emacs/23.3/lisp/textmodes/makeinfo.elc emacs23-el: /usr/share/emacs/23.3/lisp/textmodes/makeinfo.el.gz [...] if updated regularly apt-file's database will contain every files in every package in debian. -- Rémi Vanicat
Re: [O] org-list-indent-offset only works partially
Michael Brand writes: > Hi Nicolas > > Now I understand that > > - 1 :: item 1 > [TAB]- item 2 > > works as expected, when assuming that you don't want the space after > the "-" to change the indentation similar to Emacs Electric C but want > to keep only TAB, C-c and the modified cursor keys to change the > indentation. BTW, were there considerations or discussions about > "electric indentation" for lists (space after the "-")? C-c C-c changes indentation by side-effect. Its purpose is to repair the current list, which is broken if you use "[TAB]-". Also don't forget M-RET to insert an new item. I strongly suggest that binding which does a lot more than simply adding one bullet (renumbering if necessary, updating of checkboxes, etc.). I usually do M-RET and possibly TAB until the item has the correct indentation. Knowing that, I don't see any necessity for an "electric indentation". Though, to answer your question, I don't think this has ever been discussed. > So, for what I want to do I have to use > > - 1 :: item 1 > -[TAB]item 2 "M-RET TAB" will be enough. > Is the following also doing what is expected? > > - 1 :: item 1 > [TAB]-[TAB][TAB]item 2 I don't know what is expected here. Again, since you press "[TAB]-" you're creating a broken list. First use C-c C-c to repair it, then you can expect something out of it. Regards, -- Nicolas Goaziou
Re: [O] Recurring events with exceptions
Skip Collins writes: >> ,[ C-h f org-clone-subtree-with-time-shift RET ] >> > >> I find that this exactly what you are describing: I define an entry, >> clone it (with weekly shift, for instance) and then delete the >> exceptions and maybe add a few extras. If any weekly instance has to >> change, I simply change it! Works pretty well and handles all the cases >> you mentioned. > > There is one important feature lacking in the use of time-shifted > clones as a way to generate repeating events: there is nothing to bind > individual instances into a collection. A common EVENTID property > would allow for the development of tools for handling a whole series > as a group to do things like deleting, shifting, and making other > changes en masse. It seems like a simple thing to add. I'm probably missing a key point but can you not simply put a property in a higher level heading that encloses all the cloned entries? > Flexibility like this is why I like working in org. I would move my > calendar to org if I were not stuck with outlook/exchange at work. I'm > still waiting for someone to create the ultimate org/exchange sync > solution. Yes, I have been informed that we are moving to Outlook/exchange in the new year, something I am dreading... Matthieu Lemerre, on this list back in late June (Message-ID: <871uygg1fs@free.fr>), posted a (partial?) solution that helped in this regard. I've not tried that solution as I don't have to use Outlook yet. Search the mailing list. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.7 (release_7.7.381.g05ea.dirty)
Re: [O] [babel] Verbatim output from SQL command
Hi Eric, Eric Schulte wrote: >> Babel seems to interpret every *leading space* as *one empty column*. >> Normal, feature, bug? >> >> Is there some workaround to this? I thought stating "scalar" would really >> completely override any interpretation... > > I've just pushed up a fix which should resolve this issue. It does better things, but at least at the wrong place. --8<---cut here---start->8--- #+BABEL: :engine msosql :cmdline -S -U -P -d -n -w 700 :results output #+begin_src sql :eval yes :results scalar EXEC sp_helptext 'reset_me' #+end_src --8<---cut here---end--->8--- becomes, after evaluation (indented for the sake of clarity): --8<---cut here---start->8--- #+BABEL: :engine msosql :cmdline -S -U -P -d -n -w 700 :results output Text --- CREATE PROCEDURE reset_me @pfi varchar(16) AS BEGIN PRINT 'Done!' END #+begin_src sql :eval yes :results scalar EXEC sp_helptext 'reset_me' #+end_src #+results: #+begin_example #+BABEL: :engine msosql :cmdline -S -U -P -d -n -w 700 :results output Text --- CREATE PROCEDURE reset_me @pfi varchar(16) AS BEGIN PRINT 'Done!' END #+begin_src sql :eval yes :results scalar EXEC sp_helptext 'reset_me' #+end_src #+end_example --8<---cut here---end--->8--- In short, it seems that: - results is inserted at point's position (in the above case, I was using the eval speed command `e', thus being at #). - the results is duplicated, with some part of the source buffer being repeated as well... See the presence of 2 `#+BABEL:' lines in the buffer, after the evaluation. - depending on the point from which I run the code evaluation, there is (or there isn't) an `#+begin_example' directive. The `#+end_example' is always present. Best regards, Seb -- Sebastien Vauban
Re: [O] Cdlatex questions
On 17.10.2011, at 21:55, Rasmus wrote:
> Hi,
>
> I would like to add to cdlatex. However, it does not seem to work.
> This is probably the best place to ask.
>
> First, I want to add \mathbb{·} to cdlatex-math-modify-alist.
>
> Second, I want to change \mathbf{·} to \boldsymbol{·}, which is nicer
> and works with greek letters.
>
> I have tried to add the following code:
>
> #+begin_src emacs-lisp
> (add-to-list 'cdlatex-math-modify-alist
> '(98 "\\boldsymbol" "\\textbf" t nil nil))
>
> (add-to-list 'cdlatex-math-modify-alist
> '(115 "\\mathbb" nil t nil nil))
> #+end_src
Hi Rasmus,
you need to set these variables before cdlatex.el has been loaded, or you need
run (cdlatex-reset-mode) after you have changed them. THis is not documented
well,
unfortunately.
>
> However, it does not work; should I do something else to add symbols to
> cdlatex?
>
> Third, I would like to change the cdlatex-math symbol to something less
> annoying. I have tried
>
> #+begin_src emacs-lisp
> (org-defkey org-cdlatex-mode-map "¨" 'cdlatex-math-symbol)
> #+end_src
>
> However, this does not catch all cases, and for example "¨ ¨" will not
> go to the second page. Is there an easy way to change '`'.
You also need to change `cdlatex-math-symbol-prefix'.
HTH
- Carsten
>
> –Rasmus
>
> --
> Sent from my Emacs
>
>
Re: [O] A more "universal markup" for exporters with italics/quotes?
Hi, On 10/18/11 10:14 PM, John Hendy wrote: - italics: org doesn't handle multiple line italics in between / and /. Tip: You can customize org-emphasis-regexp-components to accept more than one newline. Could there be something like #+begin_quote There is! It makes blockquotes. Just go ahead and use it. Yours, Christian
Re: [O] outline-demote incorrectly demotes leaf nodes
On 18.10.2011, at 20:03, Sanjoy Mahajan wrote:
> Christian Moe christianmoe.com> writes:
>
>> The Org manual (2.5 Structure editing) says to use M-S-≤right>
>> (org-demote-subtree) for what the submitter wants to do.
>
> (I am the original reporter of the issue on the Debian BTS.) That is useful
> information for me, and I will use those keys.
>
> I do worry about one point, namely that C-c C-> (outline-demote) should still
> work. And it does work in regular outline mode. For example, if I rename my
> test file to c.otl and then use C-c C-> on the main heading, all the subtrees
> are demoted as I expected. Whereas in org mode the leaf subtree gets a space
> instead of a * when it is being demoted.
The reason for this is because in outline mode, headings are starting with
a number of stars, while in Org-mode, they start with stars followed
by a space. So "***News" is a heading in outline-mode, but not in Org-mode,
where you'd have to use "*** News".
When outline-mode tries to invent a new heading during demoting, it replicates
the last character in the headline marker, and that will be a star in
outline-mode
and the space in Org-mode.
We could fix this by defining outline-headling-alist in org-mode. For example,
you could do it like this:
(add-hook 'org-mode-hook
(lambda ()
(setq outline-heading-alist '(("* " . 1) ("** " . 2) ..
and make sure to mention all levels you might possibly every use.
However, Org-mode is not outline mode, and there is no guarantee that
outline functions will work.
Another option, if you prefer the C-> and C-< bindings is this:
(add-hook 'org-mode-hook
(lambda ()
(define-key org-mode-map [(control ?<)] 'org-promote-subtree)
(define-key org-mode-map [(control ?>)] 'org-demote-subtree)))
HTH
- Carsten
