Re: [O] Testing: org-export-e-html

[William Crandall]

Jambunathan,

Thanks to you, and Nicolas, for your patience.

I now see (blindingly, now that I do see) that the export engine
adds the # to internal links, not me.

The only trailing issue I see is the "soft error" of no  tag
on <> (see W3C notes below).



This (org):

Link and description, to anchor in paragraph: [[bc][BC]]

Paragraph with a /dedicated target/: <>BC


Exports to (new):


Link and description, to anchor in paragraph: BC


Paragraph with a dedicated target: BC



Success!




And headlines with a <> are also fine:

This (org):

Link and description, to anchor in headline: [[directors][Directors]]

* <>Directors


Exports to (new):


Link and description, to anchor in headline: Directors



Directors



Success!



And I /understand/ how ":PROPERTIES: :CUSTOM_ID: directors" in
a headline, can be linked to with: [[#directors][Directors]],
WITH a # that I, not the engine, insert.


So I'm good to go! Many thanks.





One trailing point:

You may want to consider adding a formal closing  tag for
<> elements (as the "old" engine does) rather than just
"self-closing" the  tag with a "/>".


A Firefox comment (viewing source) caught my attention:

"Self-closing syntax ("/>") used on a non-void HTML element.
Ignoring the slash and treating as a start tag."

Then I found this:

http://www.w3.org/TR/html-markup/syntax.html#syntax-elements

"A non-void element must have an end tag, unless the subsection
for that element in the HTML elements section of this reference
indicates that its end tag can be omitted."

And this:

http://www.w3.org/TR/html-markup/a.html#a-tags

"An a element must have both a start tag and an end tag."

--

I take all of this to mean that "it would be best" to use ""
closing tags, rather than "self-closing" an "".

But again, the way it is works for me. Many thanks.

Best of luck on the rest of it!

-BC


On Fri, Jun 1, 2012 at 10:04 PM, Jambunathan K  wrote:
>
> Crandall
>
> There is some confusion on your end :-).

[O] Org, Org-mode, Orgmode, Org Mode

[Achim Gratz]

Looking at the documentation and also the website and Worg, I see that
we still use all these monikers interchangeably in both capitalized and
lowercase form throughout.  I seem to remember that there was some
discussion that only one of them should be used going forward, but I
can't find it...


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [O] encoding problem

[Julien Cubizolles]

Eric S Fraga  writes:


> I used to have this problem and it was incredibly annoying.  I also
> started adding the line Bernt suggests but I kept forgetting for new
> files.  I finally solved this problem by adding the following lines to
> my emacs initialisation:
>
> #+begin_src emacs-lisp
> (prefer-coding-system 'utf-8)
> (set-charset-priority 'unicode)
> (setq default-process-coding-system '(utf-8-unix . utf-8-unix))
> #+end_src

I'll give it a try, thanks for your suggestion. I think my encoding
problems come from the many copy-paste I made from web pages (wikipedia
mostly) to org-files. I didn't think it would mess anything since
wikipedia pages are encoded in utf-8, or so I thought.

Julien.

Re: [O] Org, Org-mode, Orgmode, Org Mode

[Thorsten Jolitz]

Achim Gratz  writes:

> Looking at the documentation and also the website and Worg, I see that
> we still use all these monikers interchangeably in both capitalized and
> lowercase form throughout.  I seem to remember that there was some
> discussion that only one of them should be used going forward, but I
> can't find it...
>
>
> Regards,
> Achim.

look at:
/org-mode/doc/Documentation_Standards.org

in your Org-mode (?) distribution

-- 
cheers,
Thorsten

[O] alignment of description list in Org and export old and new

[Michael Brand]

Hi all

Is there a way to have automatic alignments in the Org buffer with M-q
(fill-paragraph) and C-c C-c like:

  - cmd ::short term + short descr
  - cmd -o   :: short term + short descr
  - cmd --log-level=err -o   ::
  long term + short descr
  - cmd --create-file ::  short term + long descr bla bla bla bla
  bla bla bla bla bla bla bla bla bla bla
  bla bla bla bla bla bla bla bla bla
  - cmd --log-level=wrn -o   ::
  long term + long descr bla bla bla bla
  bla bla bla bla bla bla bla bla bla bla
  bla bla bla bla bla bla bla bla bla
  - cmd --log-level=dbg -o   ::
  - term descr 1
  - term descr 2

instead of the default (shown below)?

With a configuration for the character column of the left alignment of
descr that is ideally per list?

Can description lists during export to ASCII, HTML, LaTeX, PDF and ODT
have descr also:
- on the same line as the term when the term is short?
- aligned horizontally?

Some remarks:

Alternatives for the long items could be:

  - cmd --log-level=err -o   ::
  long term + short descr
  - cmd --create-file ::  short term + long descr bla bla bla bla
   bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
   bla bla bla
  - cmd --log-level=wrn -o   ::
  long term + long descr bla bla bla bla
   bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
   bla bla bla

or maybe simply:

  - cmd --log-level=err -o   ::
   long term + short descr
  - cmd --create-file ::
   short term + long descr bla bla bla bla bla bla bla bla bla bla
   bla bla bla bla bla bla bla bla bla bla bla bla bla
  - cmd --log-level=wrn -o   ::
   long term + long descr bla bla bla bla bla bla bla bla bla bla
   bla bla bla bla bla bla bla bla bla bla bla bla bla

The default alignment is:

  - cmd :: short term + short descr
  - cmd -o   :: short term + short descr
  - cmd --log-level=err -o   :: long term + short descr
  - cmd --create-file :: short term + long descr bla bla bla bla bla
   bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
   bla bla
  - cmd --log-level=wrn -o   :: long term + long descr bla
   bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
   bla bla bla bla bla bla
  - cmd --log-level=dbg -o   ::
- term descr 1
- term descr 2

M-q on the item "long term + long descr" that is aligned manually as
shown first will be stable only after a second M-q instead of already
after the first M-q with release_7.8.10-633 on 23.3.1.

Michael

[O] new exporter corrupts ODT

[Michael Brand]

Hi all

If OpenOffice.org 3.2.0 is too old to count please tell me and forget.

With an Org file containing only "* a\n" the old exporter is ok but the
new exporter release_7.8.10-633 on 23.3.1 makes an ODT reported as
"corrupt" by OOo. Attached are the Org and ODT exported as old, new
and new repaired by OOo 3.2.0.

Michael


release_7.8.10-633.org
Description: Binary data


release_7.8.10-633.org.new.odt
Description: application/vnd.oasis.opendocument.text


release_7.8.10-633.org.new.odt.repaired_3_2_0.odt
Description: application/vnd.oasis.opendocument.text


release_7.8.10-633.org.old.odt
Description: application/vnd.oasis.opendocument.text

Re: [O] Org, Org-mode, Orgmode, Org Mode

[Achim Gratz]

Thorsten Jolitz writes:
> look at:
> /org-mode/doc/Documentation_Standards.org

I know and FWIW I think these are all good suggestions.  However, I seem
to remember that this was again discussed when the printed Org mode
manual was in preparation.  Our "official" website seems to have
semi-standardized on Org-mode (hyphenated), while the info manual mostly
uses Org mode (with a space).

So my question still stands, which variant is the preferred one if any
and should we work to standardize it across all documentation?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

Re: [O] Org, Org-mode, Orgmode, Org Mode

[Thorsten Jolitz]

Achim Gratz  writes:

> So my question still stands, which variant is the preferred one if any
> and should we work to standardize it across all documentation?

It would indeed be very usefull to have that written in stone once and forever,
I personally like Org-mode best.

-- 
cheers,
Thorsten

Re: [O] Org, Org-mode, Orgmode, Org Mode

[Bastien]

Hi Achim and Thorsten,

Achim Gratz  writes:

> So my question still stands, which variant is the preferred one if any
> and should we work to standardize it across all documentation?

The documentation standards states:

 - Prefer "Org mode" to "Org-mode" or "org-mode".  This is simply
   because it reflects an existing convention in The Emacs Manual which
   consistently documents mode names in this form -- "Text mode",
   "Outline mode", "Mail mode" etc.

I think it should also apply for the website.

I updated the website to use "Org mode" instead of "Org-mode" and
"Org-Mode".

-- 
 Bastien

Re: [O] Testing: org-export-e-html

[Jambunathan K]

> The only trailing issue I see is the "soft error" of no  tag
> on <> (see W3C notes below).

> http://www.w3.org/TR/html-markup/a.html#a-tags
>
> "An a element must have both a start tag and an end tag."

This is now fixed.

[O] Talk about Org mode at a small hacker conference (GPN12)

[Florian Adamsky]

Hello,

I will give a talk [fn:1] next weekend about Org mode at a small hacker
conference in Germany: Gulaschprogrammiernacht 2012 [fn:2]. There will
be around 300 people and I hope I can awake enthusiasm for Org mode. My
talk will be recorded and I once I finished my slides I will put them on
my web page. Just for your information. If somebody by chance is also
there, I would love to drink a beer with you :-).

Best regards,
Florian

[fn:1] https://entropia.de/GPN12:Emacs_Org-mode
[fn:2] https://entropia.de/GPN
--
Florian Adamsky
http://florian.adamsky.it/

[O] Bug: Images in Latex [7.8.11 (release_7.8.11-33-g2d71a5 @ /Users/petr/Dropbox/emacs/elisp/org-mode/lisp/)]

[Petr Samarin]

Including images like this results in
\href{t}{./pics/verification\_RoI\_results/BugAndItsSource.pdf} in
Latex:

#+CAPTION: A bug and its source.
#+LABEL: fig:BugAndItsSource
#+ATTR_LaTeX: width=1.0\textwidth placement=[H]
[[./pics/verification_RoI_results/BugAndItsSource.pdf]]

Emacs  : GNU Emacs 24.0.50.1 (x86_64-apple-darwin10.4.0, NS 
apple-appkit-1038.32)
of 2010-07-12 on koopa.local
Package: Org-mode version 7.8.11 (release_7.8.11-33-g2d71a5 @ 
/Users/petr/Dropbox/emacs/elisp/org-mode/lisp/)

current state:
==
(setq
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-export-latex-listings t
org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
org-agenda-files '("~/Dropbox/Productivity/GTD.org")
org-metaup-hook '(org-babel-load-in-session-maybe)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-archive-location "~/Dropbox/WorkPlans/Archive.org::"
org-after-todo-statistics-hook '(org-summary-todo)
org-export-latex-format-toc-function 'org-export-latex-format-toc-default
org-latex-to-pdf-process '("latex -shell-escape -interaction nonstopmode 
-output-directory %o %f; \n bibtex %b; \n latex -interaction 
nonstopmode -output-directory %o %f;\n pdflatex -interaction 
nonstopmode -output-directory %o %f")
org-tab-first-hook '(org-hide-block-toggle-maybe 
org-src-native-tab-command-maybe
  org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
org-confirm-shell-link-function 'yes-or-no-p
org-export-first-hook '(org-beamer-initialize-open-trackers
 (lambda nil (load-library "org-latex")
  (setq org-export-latex-listings t)
  (add-to-list (quote org-export-latex-classes)
   (quote
("org-article"
 "\\documentclass{org-article}\n
   [NO-DEFAULT-PACKAGES]\n   [PACKAGES]\n   
[EXTRA]"
 ("\\section{%s}" . "\\section*{%s}")
 ("\\subsection{%s}" . "\\subsection*{%s}")
 ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
 ("\\paragraph{%s}" . "\\paragraph*{%s}")
 ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
)
   )
  (add-to-list (quote org-export-latex-classes)
   (quote
("IEEEtran" "\\documentclass{IEEEtran}"
 ("\\section{%s}" . "\\section*{%s}")
 ("\\subsection{%s}" . "\\subsection*{%s}")
 ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
 ("\\paragraph{%s}" . "\\paragraph*{%s}")
 ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
)
   )
  )
 )
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-babel-pre-tangle-hook '(save-buffer)
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
org-export-latex-classes '(("IEEEtran" "\\documentclass{IEEEtran}"
 ("\\section{%s}" . "\\section*{%s}")
 ("\\subsection{%s}" . "\\subsection*{%s}")
 ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
 ("\\paragraph{%s}" . "\\paragraph*{%s}")
 ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
("org-article"
 "\\documentclass{org-article}\n
   [NO-DEFAULT-PACKAGES]\n   [PACKAGES]\n   
[EXTRA]"
 ("\\section{%s}" . "\\section*{%s}")
 ("\\subsection{%s}" . "\\subsection*{%s}")
 ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
 ("\\paragraph{%s}" . "\\paragraph*{%s}")
 ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
("article" "\\documentclass[11pt]{article}"
 ("\\section{%s}" . "\\section*{%s}")
 ("\\subsection{%s}" . "\\subsection*{%s}")
 ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
 ("\\paragraph{%s}" . "\\paragraph*{%s}")
 ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
("report" "\

Re: [O] Bug: Images in Latex [7.8.11 (release_7.8.11-33-g2d71a5 @ /Users/petr/Dropbox/emacs/elisp/org-mode/lisp/)]

[Jambunathan K]

Have you tried the new exporter?

1. Add contrib/lisp to load-path
2. M-x load-library RET org-export RET
3. M-x org-export-dispatch RET

You will have to migrate your existing config to the new exporter.

M-x customize-group RET org-export-e-latex RET (Note the presence of
"e").

Search for org-e-latex in this mailing list, if you run into any issues.




Petr Samarin  writes:

> Including images like this results in
> \href{t}{./pics/verification\_RoI\_results/BugAndItsSource.pdf} in
> Latex:
>
> #+CAPTION: A bug and its source.
> #+LABEL: fig:BugAndItsSource
> #+ATTR_LaTeX: width=1.0\textwidth placement=[H]
> [[./pics/verification_RoI_results/BugAndItsSource.pdf]]
>
> Emacs  : GNU Emacs 24.0.50.1 (x86_64-apple-darwin10.4.0, NS 
> apple-appkit-1038.32)
> of 2010-07-12 on koopa.local
> Package: Org-mode version 7.8.11 (release_7.8.11-33-g2d71a5 @ 
> /Users/petr/Dropbox/emacs/elisp/org-mode/lisp/)
>
> current state:
> ==
> (setq
> org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
> org-export-latex-listings t
> org-speed-command-hook '(org-speed-command-default-hook 
> org-babel-speed-command-hook)
> org-agenda-files '("~/Dropbox/Productivity/GTD.org")
> org-metaup-hook '(org-babel-load-in-session-maybe)
> org-after-todo-state-change-hook '(org-clock-out-if-current)
> org-archive-location "~/Dropbox/WorkPlans/Archive.org::"
> org-after-todo-statistics-hook '(org-summary-todo)
> org-export-latex-format-toc-function 'org-export-latex-format-toc-default
> org-latex-to-pdf-process '("latex -shell-escape -interaction nonstopmode 
> -output-directory %o %f; \n bibtex %b; \n latex -interaction 
> nonstopmode -output-directory %o %f;\n pdflatex -interaction 
> nonstopmode -output-directory %o %f")
> org-tab-first-hook '(org-hide-block-toggle-maybe 
> org-src-native-tab-command-maybe
> org-babel-hide-result-toggle-maybe 
> org-babel-header-arg-expand)
> org-src-mode-hook '(org-src-babel-configure-edit-buffer 
> org-src-mode-configure-edit-buffer)
> org-confirm-shell-link-function 'yes-or-no-p
> org-export-first-hook '(org-beamer-initialize-open-trackers
>(lambda nil (load-library "org-latex")
> (setq org-export-latex-listings t)
> (add-to-list (quote org-export-latex-classes)
>  (quote
>   ("org-article"
>"\\documentclass{org-article}\n
>[NO-DEFAULT-PACKAGES]\n   [PACKAGES]\n 
>   [EXTRA]"
>("\\section{%s}" . "\\section*{%s}")
>("\\subsection{%s}" . "\\subsection*{%s}")
>("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>("\\paragraph{%s}" . "\\paragraph*{%s}")
>("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
>   )
>  )
> (add-to-list (quote org-export-latex-classes)
>  (quote
>   ("IEEEtran" "\\documentclass{IEEEtran}"
>("\\section{%s}" . "\\section*{%s}")
>("\\subsection{%s}" . "\\subsection*{%s}")
>("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>("\\paragraph{%s}" . "\\paragraph*{%s}")
>("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
>   )
>  )
> )
>)
> org-agenda-before-write-hook '(org-agenda-add-entry-text)
> org-babel-pre-tangle-hook '(save-buffer)
> org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
> org-cycle-show-empty-lines 
> org-optimize-window-after-visibility-change)
> org-export-latex-classes '(("IEEEtran" "\\documentclass{IEEEtran}"
>("\\section{%s}" . "\\section*{%s}")
>("\\subsection{%s}" . "\\subsection*{%s}")
>("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>("\\paragraph{%s}" . "\\paragraph*{%s}")
>("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
>   ("org-article"
>"\\documentclass{org-article}\n
>[NO-DEFAULT-PACKAGES]\n   [PACKAGES]\n 
>   [EXTRA]"
>("\\section{%s}" . "\\section*{%s}")
>("\\subsection{%s}" . "\\subsection*{%s}")
>("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>("\\paragraph{%s}" . "\\paragraph*{%s}")
>("\\subparagraph{%s}" . "\\subparagraph*{%s}"))

Re: [O] new exporter corrupts ODT

[Jambunathan K]

Michael Brand  writes:

> Hi all
>
> If OpenOffice.org 3.2.0 is too old to count please tell me and forget.
>
> With an Org file containing only "* a\n" the old exporter is ok but the
> new exporter release_7.8.10-633 on 23.3.1 makes an ODT reported as
> "corrupt" by OOo. Attached are the Org and ODT exported as old, new
> and new repaired by OOo 3.2.0.

I am not able to reproduce this issue locally.  My LibreOffice is fairly
recent. (LibreOffice 3.5.2.2 Build ID: 281b639-6baa1d3-ef66a77-d866f25-f36d45f)

If I pass the corrupted file through an online validator [1], I get the
below error.  The culprit is the mimetype file.  Note the leading
whitespace and the trailing newline.  If I fix this extraneous
whitespace by hand, then I see that the reported corruption goes away.

,
| application/vnd.oasis.opendocument.text
`

I can confirm that ODT exporter, never creates the above leading and
trailing whitespaces.

Unless you hand-edited the ODT document, I think the error could be
because of one of the customizations you have.  (Do you have
`org-e-odt-prettify-xml' set to t.  If yes, what mode does mimetype file
open for you.  For me, mimetype opens in Fundamental mode.)

,
| ODF Validator Result Page
| Result for release_7.8.10-633.org.new.odt
| 
| The document is NOT conformant ODF1.2!
| Details:
| release_7.8.10-633.org.new.odt: Info: ODF version of root document: 1.2
| release_7.8.10-633.org.new.odt/mimetype: Error: The ODF package 
'release_7.8.10-633.org.new.odt' contains a 'mimetype' file containing ' 
application/vnd.oasis.opendocument.text', which differs from the mediatype of 
the root document 'application/vnd.oasis.opendocument.text'!
| release_7.8.10-633.org.new.odt: Error: The ODF mimetype ' 
application/vnd.oasis.opendocument.text' is invalid for the ODF XML Schema 
document!
| release_7.8.10-633.org.new.odt/mimetype: Info: mimetype is not an 
ODFMediaTypes mimetype.
| internal:/schema/odf1.2/OpenDocument-v1.2-cos01-manifest-schema.rng: Info: 
parsed.
| release_7.8.10-633.org.new.odt/META-INF/manifest.xml: Info: no errors, no 
warnings
| release_7.8.10-633.org.new.odt/mimetype: Info: 1 errors, no warnings
| release_7.8.10-633.org.new.odt: Info: Media Type: 
application/vnd.oasis.opendocument.text
| internal:/schema/odf1.2/OpenDocument-v1.2-cos01-schema.rng: Info: parsed.
| release_7.8.10-633.org.new.odt/meta.xml: Info: Generator: Generated by Org 
mode 7.8.10 in Emacs 23.3.1.
| release_7.8.10-633.org.new.odt/meta.xml: Info: no errors, no warnings
| release_7.8.10-633.org.new.odt/styles.xml: Info: no errors, no warnings
| release_7.8.10-633.org.new.odt/content.xml: Info: no errors, no warnings
| internal:/schema/odf1.2/OpenDocument-v1.2-cos01-dsig-schema.rng: Info: parsed.
| release_7.8.10-633.org.new.odt: Info: 2 errors, no warnings
`


Footnotes: 
[1]  http://odf-validator.rhcloud.com/

-- 

Re: [O] new exporter corrupts ODT

[Jambunathan K]

Jambunathan K  writes:

> I think the error could be because of one of the customizations you
> have.

Good way to check this is with:

"C:\Program Files\emacs-24.0.97\bin\runemacs.exe" -Q -L
~/src/org-mode/lisp/ -L ~/src/org-mode/contrib/lisp/

(Note the -Q and adjusted load-paths)

M-x load-library RET org-e-odt RET
M-x org-export-dispatch RET etc etc

-- 

Re: [O] Org, Org-mode, Orgmode, Org Mode

[Gregory Benjamin]

Hello all,

On Sat, Jun 02, 2012 at 12:11:48PM +0200, Bastien wrote:
> Hi Achim and Thorsten,
> 
> Achim Gratz  writes:
> 
> > So my question still stands, which variant is the preferred one if any
> > and should we work to standardize it across all documentation?
> 
> The documentation standards states:
> 
>  - Prefer "Org mode" to "Org-mode" or "org-mode".  This is simply
>because it reflects an existing convention in The Emacs Manual which
>consistently documents mode names in this form -- "Text mode",
>"Outline mode", "Mail mode" etc.
> 
> I think it should also apply for the website.
> 
> I updated the website to use "Org mode" instead of "Org-mode" and
> "Org-Mode".

I believe Org-mode is vastly superior to the alternatives because the
hyphen links the two little words into a fairly unique pattern that
results in pertinent results from search engines.

I believe every effort should be made to adopt Org-mode universally;
to use Org mode instead will make Org-mode material much harder to
find on the internet. 

Furthermore, to invoke Org-mode from inside Emacs, one types "M-x
org-mode", not "M-x org mode".

--
Greg Benjamin

Re: [O] Talk about Org mode at a small hacker conference (GPN12)

[Thorsten Jolitz]

Florian Adamsky  writes:

Hello Florian, 

> I will give a talk [fn:1] next weekend about Org mode at a small hacker
> conference in Germany

Karlsruhe is too far away for me, unfortunately. However, I'm really
impressed by the beautiful design of your homepage:

,-
| > http://florian.adamsky.it/
| 
| About this site
| 
| I created this site with Emacs, org-mode, Git and Jekyll. I used this
| wunderful clean design from Steve Losh and modified it a little bit. All
| kudos belong to him.
`-

I visited the homepage of Steve Losh and his Mercurial repository for
the page. Since I want to build an Org mode based homepage too, I would
really like to 'steal' this design. Do you mind to share how you combined
Steve Losh's design with Org mode, Git and Jekyll? Is there a public
repo of your sites code?

TIA

-- 
cheers,
Thorsten

Re: [O] Org, Org-mode, Orgmode, Org Mode

[Gregor Zattler]

Hi Gregory,
* Gregory Benjamin  [02. Jun. 2012]:
> On Sat, Jun 02, 2012 at 12:11:48PM +0200, Bastien wrote:
>> The documentation standards states:
>> 
>>  - Prefer "Org mode" to "Org-mode" or "org-mode".  This is simply
>>because it reflects an existing convention in The Emacs Manual which
>>consistently documents mode names in this form -- "Text mode",
>>"Outline mode", "Mail mode" etc.
>> 
>> I think it should also apply for the website.
>> 
>> I updated the website to use "Org mode" instead of "Org-mode" and
>> "Org-Mode".
> 
> I believe Org-mode is vastly superior to the alternatives because the
> hyphen links the two little words into a fairly unique pattern that
> results in pertinent results from search engines.
>
> I believe every effort should be made to adopt Org-mode universally;
> to use Org mode instead will make Org-mode material much harder to
> find on the internet. 

Most, especially "the" search engine allows for quoted "org mode"
searches...
 
> Furthermore, to invoke Org-mode from inside Emacs, one types "M-x
> org-mode", not "M-x org mode".

True.

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: [O] new exporter corrupts ODT

[Jambunathan K]

Jambunathan K  writes:

> Unless you hand-edited the ODT document, I think the error could be
> because of one of the customizations you have.  (Do you have
> `org-e-odt-prettify-xml' set to t.  If yes, what mode does mimetype
> file open for you.  For me, mimetype opens in Fundamental mode.)

After sending out the email, I realized that `org-e-odt-prettify-xml' is
ON by default in the org-e-odt.el.  Now I have turned it off.

Hopefully things are OK at your end with this "fix".  I am still curious
what mode does mimetype file open for you. (Do M-: mode-name in mimetype
buffer)

If the problem persists (even after this), try emacs -Q and isolate your
local config that messes up things.

-- 

[O] Possible to insert and view picture in a .org file?

[itm...@chrikro.net]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi!

Is it possible to insert and view picture in a .org file with emacs?
I want to se the picture in the text while editing the .org file.
Possible?

By
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (MingW32)

iEYEARECAAYFAk/KMd4ACgkQ2+bVj21Y+8lOKgCfYe5pXqdl3+MToY02pnUfPHuv
/0UAn3Xn13s5hNvCcZwn8VoscyW171DA
=G8wp
-END PGP SIGNATURE-

Re: [O] Org, Org-mode, Orgmode, Org Mode

[suvayu ali]

On Sat, Jun 2, 2012 at 12:11 PM, Bastien  wrote:
> Hi Achim and Thorsten,
>
> Achim Gratz  writes:
>
>> So my question still stands, which variant is the preferred one if any
>> and should we work to standardize it across all documentation?
>
> The documentation standards states:
>
>  - Prefer "Org mode" to "Org-mode" or "org-mode".  This is simply
>   because it reflects an existing convention in The Emacs Manual which
>   consistently documents mode names in this form -- "Text mode",
>   "Outline mode", "Mail mode" etc.
>
> I think it should also apply for the website.
>
> I updated the website to use "Org mode" instead of "Org-mode" and
> "Org-Mode".
>

The above suggestion is very reasonable and consistent with the rest of
Emacs. But I would like to point out I have seen Carsten mostly use
"Org-mode". Here is one example:


:)

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] Possible to insert and view picture in a .org file?

[Jambunathan K]

"itm...@chrikro.net"  writes:

> Hi!
>
> Is it possible to insert and view picture in a .org file with emacs?
> I want to se the picture in the text while editing the .org file.
> Possible?

(Self-service)

M-x org-info RET

Within info buffer, 

i inline TAB

-- 

Re: [O] new exporter corrupts ODT

[Michael Brand]

Hi Jambunathan

On Sat, Jun 2, 2012 at 5:18 PM, Jambunathan K  wrote:
> After sending out the email, I realized that `org-e-odt-prettify-xml' is
> ON by default in the org-e-odt.el.  Now I have turned it off.
>
> Hopefully things are OK at your end with this "fix".

Thank you for looking into this.

I just pulled and now get a backtrace when trying this:

cd /f/xmirror/git/org-mode
git pull
git describe
==> release_7.8.10-642-gca6f523
make cleanall info autoloads
(/Applications/Emacs.app/Contents/MacOS/Emacs -Q \
-L "/f/xmirror/git/org-mode/lisp/" \
-L "/f/xmirror/git/org-mode/contrib/lisp/" &)
M-x load-library RET org-e-odt RET
C-x C-f release_7.8.10-633.org RET
M-x org-export-dispatch RET o
==> see attached backtrace

> I am still curious
> what mode does mimetype file open for you. (Do M-: mode-name in mimetype
> buffer)

"M-: mode-name RET" shows "Fundamental".

Michael
Debugger entered--Lisp error: (void-function org-e-html-encode-plain-text)
  (org-e-html-encode-plain-text line)
  (setq line (org-e-html-encode-plain-text line))
  org-e-odt-encode-plain-text("a" t)
  (setq text (org-e-odt-encode-plain-text text t))
  org-e-odt-plain-text("a" (:author "br" :creator "Generated by Org mode 7.8.10 
in Emacs 23.3.1." :date nil :description nil :email "b@aHostName" :exclude-tags 
("noexport") :headline-levels 3 :keywords nil :language "en" :preserve-breaks 
nil :section-numbers t :select-tags ("export") :time-stamp-file t :title 
"release_7.8.10-633" :with-archived-trees headline :with-author t :with-clocks 
nil :with-creator comment :with-drawers t :with-email nil :with-emphasize t 
:with-entities t :with-fixed-width t :with-footnotes t :with-plannings nil ...))
  funcall(org-e-odt-plain-text "a" (:author "br" :creator "Generated by Org 
mode 7.8.10 in Emacs 23.3.1." :date nil :description nil :email "b@aHostName" 
:exclude-tags ("noexport") :headline-levels 3 :keywords nil :language "en" 
:preserve-breaks nil :section-numbers t :select-tags ("export") 
:time-stamp-file t :title "release_7.8.10-633" :with-archived-trees headline 
:with-author t :with-clocks nil :with-creator comment :with-drawers t 
:with-email nil :with-emphasize t :with-entities t :with-fixed-width t 
:with-footnotes t :with-plannings nil ...))
  (if transcoder (funcall transcoder data info) data)
  (let ((transcoder ...)) (if transcoder (funcall transcoder data info) data))
  (org-export-filter-apply-functions (plist-get info :filter-plain-text) (let 
(...) (if transcoder ... data)) info)
  (cond ((member data ...) nil) ((eq type ...) 
(org-export-filter-apply-functions ... ... info)) ((not ...) (org-export-data 
... info)) ((not type) (mapconcat ... data "")) ((or ... ...) (let ... ...)) (t 
(let ... ...)))
  (let* ((type ...) (results ...)) (cond (... nil) (... results) (t ...)))
  org-export-data("a" (:author "br" :creator "Generated by Org mode 7.8.10 in 
Emacs 23.3.1." :date nil :description nil :email "b@aHostName" :exclude-tags 
("noexport") :headline-levels 3 :keywords nil :language "en" :preserve-breaks 
nil :section-numbers t :select-tags ("export") :time-stamp-file t :title 
"release_7.8.10-633" :with-archived-trees headline :with-author t :with-clocks 
nil :with-creator comment :with-drawers t :with-email nil :with-emphasize t 
:with-entities t :with-fixed-width t :with-footnotes t :with-plannings nil ...))
  (lambda (obj) (org-export-data obj info))("a")
  mapconcat((lambda (obj) (org-export-data obj info)) ("a") "")
  (cond ((member data ...) nil) ((eq type ...) 
(org-export-filter-apply-functions ... ... info)) ((not ...) (org-export-data 
... info)) ((not type) (mapconcat ... data "")) ((or ... ...) (let ... ...)) (t 
(let ... ...)))
  (let* ((type ...) (results ...)) (cond (... nil) (... results) (t ...)))
  org-export-data(("a") (:author "br" :creator "Generated by Org mode 7.8.10 in 
Emacs 23.3.1." :date nil :description nil :email "b@aHostName" :exclude-tags 
("noexport") :headline-levels 3 :keywords nil :language "en" :preserve-breaks 
nil :section-numbers t :select-tags ("export") :time-stamp-file t :title 
"release_7.8.10-633" :with-archived-trees headline :with-author t :with-clocks 
nil :with-creator comment :with-drawers t :with-email nil :with-emphasize t 
:with-entities t :with-fixed-width t :with-footnotes t :with-plannings nil ...))
  (let* ((numberedp ...) (level ...) (text ...) (full-text ...)) (cond (... 
nil) (... ...) (t ...)))
  org-e-odt-headline((headline (:raw-value "a" :title ("a") :begin 1 :end 5 
:pre-blank 0 :hiddenp nil :contents-begin 5 :contents-end 5 :level 1 :priority 
nil :tags nil :todo-keyword nil :todo-type nil :scheduled nil :deadline nil 
:timestamp nil :clock nil :post-blank 0 :footnote-section-p nil :archivedp nil 
:commentedp nil :quotedp nil :category nil)) nil (:author "br" :creator 
"Generated by Org mode 7.8.10 in Emacs 23.3.1." :date nil :description nil 
:email "b@aHostName" :exclude-tags ("noexport") :headline-levels 3 :keywords 
nil :language "en" :preserve-breaks 

Re: [O] Talk about Org mode at a small hacker conference (GPN12)

[Florian Adamsky]

Dear Thorsten,

Thorsten Jolitz  writes:

> Florian Adamsky  writes:
>
>> I will give a talk [fn:1] next weekend about Org mode at a small hacker
>> conference in Germany
>
> Karlsruhe is too far away for me, unfortunately. However, I'm really
> impressed by the beautiful design of your homepage:
>
> ,-
> | > http://florian.adamsky.it/
> | 
> | About this site
> | 
> | I created this site with Emacs, org-mode, Git and Jekyll. I used this
> | wunderful clean design from Steve Losh and modified it a little bit. All
> | kudos belong to him.
> `-
>
> I visited the homepage of Steve Losh and his Mercurial repository for
> the page. Since I want to build an Org mode based homepage too, I would
> really like to 'steal' this design. Do you mind to share how you combined
> Steve Losh's design with Org mode, Git and Jekyll? Is there a public
> repo of your sites code?

Sorry, but I have to disappoint you, the integration with Org mode is
simple and not very sophisticated. I just use Org mode to write my blog
posts and then to export it to HTML. After that, I put the exported HTML
file in the _posts/ directory and commit a new stage via git. My server
automatically pulls every 30 min the repository and runs the jekyll
parser after that.

The blog post file is a simple HTML file with the a small header like
the following:

---
layout: post
title: Lorem ipsum
---

In fact nothing really special. However, if you're still interested, I
can send you my repository.

Best regards
-- 
Florian Adamsky
http://florian.adamsky.it/

Re: [O] new exporter (was: Bug: Images in Latex..)

[Achim Gratz]

Jambunathan K writes:
> Have you tried the new exporter?
>
> 1. Add contrib/lisp to load-path
> 2. M-x load-library RET org-export RET
> 3. M-x org-export-dispatch RET

Better yet, hardlink those files in contrib/lisp you want to use into
lisp/, but remember to always edit them in contrib/lisp and never in
lisp/.  That way, the build system will handle them correctly and you
can use them from an installed org.  In case of the new exporter:

ln contrib/lisp/org-{element,export,e-*}.el lisp/

The byte compiler isn't happy with the new exporter at the moment, lots
of free variables, some variables declared later than used and some CL
macros at runtime... here's my first stab on fixing some of that:

>From d7ef1bfbaef873521731697d86112029f02cdc8b Mon Sep 17 00:00:00 2001
From: Achim Gratz 
Date: Sat, 2 Jun 2012 18:38:24 +0200
Subject: [PATCH 5/5] Make byte-compiler more happy

* contrib/lisp/org-e-ascii.el: Remove declarations and replace with
  require.

* contrib/lisp/org-e-html.el: Remove declarations and replace with
  require.

* contrib/lisp/org-e-latex.el: Remove declarations and replace with
  require.

* contrib/lisp/org-e-publish.el: Remove declarations and replace with
  require.

* contrib/lisp/org-export.el: Remove declarations and replace with
  require.  Prevent byte-compilation, it currently would produce an
  error due to circular dependencies in the file.
---
 contrib/lisp/org-e-ascii.el   |   38 --
 contrib/lisp/org-e-html.el|   41 +---
 contrib/lisp/org-e-latex.el   |   46 +
 contrib/lisp/org-e-publish.el |   22 +---
 contrib/lisp/org-export.el|   15 +-
 5 files changed, 29 insertions(+), 133 deletions(-)

diff --git a/contrib/lisp/org-e-ascii.el b/contrib/lisp/org-e-ascii.el
index c8bc334..4956b14 100644
--- a/contrib/lisp/org-e-ascii.el
+++ b/contrib/lisp/org-e-ascii.el
@@ -32,40 +32,10 @@
 
 ;;; Code:
 
-(eval-when-compile (require 'cl))
-
-(declare-function org-element-contents "org-element" (element))
-(declare-function org-element-property "org-element" (property element))
-(declare-function org-element-normalize-string "org-element" (s))
-(declare-function org-element-map "org-element"
-		  (data types fun &optional info first-match))
-
-(declare-function org-export-collect-footnote-definitions
-		  "org-export" (data info))
-(declare-function org-export-collect-headlines "org-export" (info &optional n))
-(declare-function org-export-collect-listings "org-export" (info))
-(declare-function org-export-collect-tables "org-export" (info))
-(declare-function org-export-data "org-export" (data info))
-(declare-function org-export-expand-macro "org-export" (macro info))
-(declare-function org-export-format-code-default "org-export" (element info))
-(declare-function org-export-get-coderef-format "org-export" (path desc))
-(declare-function org-export-get-footnote-number "org-export" (footnote info))
-(declare-function org-export-get-headline-number "org-export" (headline info))
-(declare-function org-export-get-ordinal "org-export"
-		  (element info &optional types predicate))
-(declare-function org-export-get-parent-headline "org-export" (blob info))
-(declare-function org-export-get-relative-level "org-export" (headline info))
-(declare-function org-export-low-level-p "org-export" (headline info))
-(declare-function org-export-output-file-name "org-export"
-		  (extension &optional subtreep pub-dir))
-(declare-function org-export-resolve-coderef "org-export" (ref info))
-(declare-function org-export-resolve-fuzzy-link "org-export" (link info))
-(declare-function org-export-resolve-id-link "org-export" (link info))
-(declare-function org-export-resolve-radio-link "org-export" (link info))
-(declare-function
- org-export-to-file "org-export"
- (backend file &optional subtreep visible-only body-only ext-plist))
-
+(eval-when-compile
+  (require 'cl))
+(require 'org-element)
+(require 'org-export)
 
 ;;; Define Back-End
 ;;
diff --git a/contrib/lisp/org-e-html.el b/contrib/lisp/org-e-html.el
index 53547a0..1f39b92 100644
--- a/contrib/lisp/org-e-html.el
+++ b/contrib/lisp/org-e-html.el
@@ -35,48 +35,17 @@
 ;;; org-e-html.el
 ;;; Dependencies
 
+(eval-when-compile
+  (require 'cl)
+  (require 'table))
+(require 'org-exp)
 (require 'org-export)
+(require 'org-lparse)
 (require 'format-spec)
-(eval-when-compile (require 'cl) (require 'table))
-
 
 
 ;;; Function Declarations
 
-(declare-function org-element-get-property "org-element" (property element))
-(declare-function org-element-normalize-string "org-element" (s))
-
-(declare-function org-export-data "org-export" (data info))
-(declare-function org-export-directory "org-export" (type plist))
-(declare-function org-export-expand-macro "org-export" (macro info))
-(declare-function org-export-first-sibling-p "org-export" (headline info))
-(declare-function org-export-footnote-first-reference-p "org-expo

Re: [O] Possible to insert and view picture in a .org file?

[itm...@chrikro.net]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jambunathan K skrev 2012-06-02 17:42:
> "itm...@chrikro.net"  writes:
> 
>> Hi!
>> 
>> Is it possible to insert and view picture in a .org file with
>> emacs? I want to se the picture in the text while editing the
>> .org file. Possible?
> 
> (Self-service)
> 
> M-x org-info RET
> 
> Within info buffer,
> 
> i inline TAB
> 

Thank you but I still can not view the picture in the org file. Any
ideas? The picture is viewable in exported html but not in orgmode in
emacs and that is what I want.

I use emacs 23.4 on win7.

/C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (MingW32)

iEYEARECAAYFAk/KWJcACgkQ2+bVj21Y+8nWqwCfcKfCZIqdjdM+qVsNvIAwVCil
AloAoNP0am2ggXKqEhIu35nusHTP+S1f
=00VQ
-END PGP SIGNATURE-

Re: [O] Possible to insert and view picture in a .org file?

[Nick Dokos]

[forgot to CC: the list - apologies for duplication]

itm...@chrikro.net  wrote:

> Jambunathan K skrev 2012-06-02 17:42:
> > "itm...@chrikro.net"  writes:
> >
> >> Hi!
> >>
> >> Is it possible to insert and view picture in a .org file with
> >> emacs? I want to se the picture in the text while editing the
> >> .org file. Possible?
> >
> > (Self-service)
> >
> > M-x org-info RET
> >
> > Within info buffer,
> >
> > i inline TAB
> >
> 
> Thank you but I still can not view the picture in the org file. Any
> ideas? The picture is viewable in exported html but not in orgmode in
> emacs and that is what I want.
> 
> I use emacs 23.4 on win7.
> 

Did you try C-c C-x C-v ?

C-h f org-toggle-inline-images RET

Nick

Re: [O] Org, Org-mode, Orgmode, Org Mode

[Samuel Wales]

Org-mode can mislead you into thinking that it is a command or a
major-mode symbol.  It is neither.  :)

So the Bikeshed Vote of the Week for me goes to Org mode in docs in
conformance with the Emacs Manual.

I'd suggest Org when referring to the entire collection of Org mode,
Orgstruct mode, Org mode format, Org vim clones, the Org way of life,
Org merchandise, the Org movie franchise, the Org anime, the Platonic
Org, etc.

Samuel

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

Re: [O] Talk about Org mode at a small hacker conference (GPN12)

[Thorsten Jolitz]

Florian Adamsky  writes:

Hi Florian,

> Thorsten Jolitz  writes:
>
>> Florian Adamsky  writes:
>>
>>> I will give a talk [fn:1] next weekend about Org mode at a small hacker
>>> conference in Germany
>>
>> Karlsruhe is too far away for me, unfortunately. However, I'm really
>> impressed by the beautiful design of your homepage:
>>
>> ,-
>> | > http://florian.adamsky.it/
>> | 
>> | About this site
>> | 
>> | I created this site with Emacs, org-mode, Git and Jekyll. I used this
>> | wunderful clean design from Steve Losh and modified it a little
>> | bit. All
>> | kudos belong to him.
>> `-
>>
>> I visited the homepage of Steve Losh and his Mercurial repository for
>> the page. Since I want to build an Org mode based homepage too, I would
>> really like to 'steal' this design. Do you mind to share how you combined
>> Steve Losh's design with Org mode, Git and Jekyll? Is there a public
>> repo of your sites code?
>
> Sorry, but I have to disappoint you, the integration with Org mode is
> simple and not very sophisticated. 

As long as it looks nice it must not be sophisticated. And its really
the kind of design I was looking for - minimal, but beautiful and with
style. 

> I just use Org mode to write my blog posts and then to export it to
> HTML. After that, I put the exported HTML file in the _posts/
> directory and commit a new stage via git. My server automatically
> pulls every 30 min the repository and runs the jekyll parser after
> that.
>
> The blog post file is a simple HTML file with the a small header like
> the following:
>
> ---
> layout: post
> title: Lorem ipsum
> ---
>
> In fact nothing really special. However, if you're still interested, I
> can send you my repository.

I'm still interested!
Would be great if you could send me the repo. 

Thanks

-- 
cheers,
Thorsten

Re: [O] Org, Org-mode, Orgmode, Org Mode

[Sebastien Vauban]

Bastien,

Bastien wrote:
> Hi Achim and Thorsten,
>
> Achim Gratz  writes:
>
>> So my question still stands, which variant is the preferred one if any
>> and should we work to standardize it across all documentation?
>
> The documentation standards states:
>
>  - Prefer "Org mode" to "Org-mode" or "org-mode".  This is simply
>because it reflects an existing convention in The Emacs Manual which
>consistently documents mode names in this form -- "Text mode",
>"Outline mode", "Mail mode" etc.
>
> I think it should also apply for the website.
>
> I updated the website to use "Org mode" instead of "Org-mode" and
> "Org-Mode".

Though, if we look at the doc, we see:

--8<---cut here---start->8---
Org Mode Manual
***

This manual is for Org version 7.8.10 (release_7.8.10-568-gc84cda).
--8<---cut here---end--->8---

ie:

- one time with capital M
- once where "Org" only is used

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] Possible to insert and view picture in a .org file?

[itm...@chrikro.net]

Nick Dokos skrev 2012-06-02 21:13:
> [forgot to CC: the list - apologies for duplication]
> 
> itm...@chrikro.net  wrote:
> 
>> Jambunathan K skrev 2012-06-02 17:42:
>>> "itm...@chrikro.net"  writes:
>>>
 Hi!

 Is it possible to insert and view picture in a .org file with
 emacs? I want to se the picture in the text while editing the
 .org file. Possible?
>>>
>>> (Self-service)
>>>
>>> M-x org-info RET
>>>
>>> Within info buffer,
>>>
>>> i inline TAB
>>>
>>
>> Thank you but I still can not view the picture in the org file. Any
>> ideas? The picture is viewable in exported html but not in orgmode in
>> emacs and that is what I want.
>>
>> I use emacs 23.4 on win7.
>>
> 
> Did you try C-c C-x C-v ?
> 
> C-h f org-toggle-inline-images RET
> 
> Nick
> 
> 
Thank you both.

Re: [O] Org, Org-mode, Orgmode, Org Mode

[Scott Randby]

On 06/02/2012 04:10 PM, Sebastien Vauban wrote:
> Bastien,
>
> Bastien wrote:
>> Hi Achim and Thorsten,
>>
>> Achim Gratz  writes:
>>
>>> So my question still stands, which variant is the preferred one if any
>>> and should we work to standardize it across all documentation?
>>
>> The documentation standards states:
>>
>>  - Prefer "Org mode" to "Org-mode" or "org-mode".  This is simply
>>because it reflects an existing convention in The Emacs Manual which
>>consistently documents mode names in this form -- "Text mode",
>>"Outline mode", "Mail mode" etc.
>>
>> I think it should also apply for the website.
>>
>> I updated the website to use "Org mode" instead of "Org-mode" and
>> "Org-Mode".
>
> Though, if we look at the doc, we see:
>
> --8<---cut here---start->8---
> Org Mode Manual
> ***
>
> This manual is for Org version 7.8.10 (release_7.8.10-568-gc84cda).
> --8<---cut here---end--->8---
>
> ie:
>
> - one time with capital M
> - once where "Org" only is used
>
> Best regards,
>   Seb
>

My habit is to use "Org-mode" when I introduce Org mode to others. I do
this so that it is understood that I'm not talking about an organization
and so that others realize that Org mode is a mode of Emacs. But this is
only a habit.

Scott Randby

Re: [O] Possible to insert and view picture in a .org file?

[Jambunathan K]

See this thread:
http://lists.gnu.org/archive/html/emacs-orgmode/2011-10/msg00792.html

You need to copy libpng (or whatever dll) to your emacs bin directory -
directory where runemacs.exe is located.

[O] Difficulty of using Org mode

[Michael Hannon]

Hi, folks.  Just FYI:


- Forwarded Message -
>From: Yihui Xie 
>To: Stephen Eglen  
>Cc: ess-h...@r-project.org 
>Sent: Saturday, June 2, 2012 3:08 PM
>Subject: Re: [ESS] knitr
> 
>There is no point comparing markdown with org mode, and the answer
>will be definitely this: org mode can beat markdown almost everywhere;
>they are not even comparable. The point is that markdown was not
>designed to provide new features; it was designed to be simple so it
>intentionally discarded lots of features and people can learn it
>quickly. I have tried a few times to learn org mode, and it is just
>too complicated for me.
>
>Regards,
>Yihui
>--
>Yihui Xie 
>Phone: 515-294-2465 Web: http://yihui.name
>Department of Statistics, Iowa State University
>2215 Snedecor Hall, Ames, IA
>
>
>On Sat, Jun 2, 2012 at 3:17 PM, Stephen Eglen  
>wrote:
>>
>> That's interesting that LaTeX was a barrier for R users.
>>
>> I've not used Markdown before; it seems neat, but what does it offer
>> that org mode doesn't?  I see there is a markdown-mode.el
>>
>> http://jblevins.org/projects/markdown-mode/
>>
>> that has some support for org mode style cycling of outlines.
>>
>> Anyone prefer markdown to org mode, and if so why?
>>
>> (If anyone is interested, on the org mode list recently there was
>> discussion about exporting org docs to markdown.)
>>
>> Stephen
>
>__
>ess-h...@r-project.org mailing list
>https://stat.ethz.ch/mailman/listinfo/ess-help
>
>
>

[O] Local subtree view

[Rebel Neurofog]

Hi, guys!

I'm finally beginning to integrate Org mode into my way of thinking.
But one thing really bothers me: local subtree view.

The closest thing I'd like to have is (org-tree-to-indirect-buffer),
but, first, there's a bug in it (I use Emacs 23.4.2 - latest official):
- When I edit the last empty line in indirect buffer, the new text
gets into next entry (inside original buffer) like this:
** TODO Go shoping
Some new text** TODO Finish Line Edit widget
- When I edit the last entry (non-empty line) in indirect buffer, the
new text is inserted into original buffer
right after ... of unexpanded branch like this:
* TODO Things to do today...New text which should be inside

Second, I'd rather edit selected subtree in local mode and then
go back to global (normal) mode instead of dealing with 2 windows.

Is there such function (did I miss it)?
If not then what do you think about the proposition?

Re: [O] Local subtree view (analysis of a fundamental issue with subtree narrowing)

[Samuel Wales]

Hi Rebel,

On 6/2/12, Rebel Neurofog  wrote:
> The closest thing I'd like to have is (org-tree-to-indirect-buffer),
> but, first, there's a bug in it (I use Emacs 23.4.2 - latest official):
> - When I edit the last empty line in indirect buffer, the new text
> gets into next entry (inside original buffer) like this:

> ** TODO Go shoping
> Some new text** TODO Finish Line Edit widget

What version of Org are you running?  My version works.  That
apparently empty line is possibly the beginning of the next line.  It
might need a newline.  That is expected.

This is /related to/ a subtle issue in which Org calls an Outline mode
function that is arguably counterintuitive and dangerous.  That
function does not include the final newline, which has led to buffer
corruption bugs.  I reported one long ago with sorting in indirect
buffers.  IMO narrowing should always include the final newline, but
it is a potentially involved discussion.

However, having an empty line at the end of your narrowed region is
expected with what I believe the correct narrowing should be, and
actually unexpected with the default way.  So your bug /should/ be
that it adds a spurious extra empty line, not that it corrupts the
next line.  :)

Maybe you added the empty line yourself, and then added text to it
without  adding a newline.

I hope that helps.

I am interested off-list in the origin of your name, if it has meaning.

Samuel

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

Re: [O] Smart Quotes Exporting

[Mark E. Shoulson]

All right, preliminary patch is attached, *maybe* good enough for more 
serious consideration now, but might need some fixes. Still only uses 
ordinary regexps and plain-text strings, but can now handle the example 
with formatting-breaks next to quotes. Things have been moved into more 
appropriate locations, made customs, docstrings and types fixed, etc, etc.


It supports onscreen display of "smart" quotes (when enabled); I have 
the quotes displayed in org-document-info face so they are slightly 
distinct, to make it clearer that they are "altered" from what they are 
in the plain text. This may or may not be a popular (or good) idea. I 
have also built it into the new export engine in org-e-latex and 
org-e-html as proofs of concept. I'm not positive the latex one will 
work properly for German, though; there might need to be something 
enabled in LaTeX for it to format ,, into „.


It should probably be set not to smartify quotes onscreen in comments; I 
haven't done that yet.


Comments welcome; I hope I didn't complicate matters in the export 
engines too much.


~mark
>From 1bc507cf69c94d5645436abc6e28e7d96999083e Mon Sep 17 00:00:00 2001
From: Mark Shoulson 
Date: Tue, 29 May 2012 23:01:12 -0400
Subject: [PATCH] Add `smart' quotes for onscreen display and for latex and
 html export

* lisp/org.el: Add `smart' quotes: custom variables to define
  regexps to recognize quotes, to define how and whether to
  display them, and org-fontify-quotes to display `smart-quote'
  characters when activated.

* contrib/lisp/org-export.el: Add function org-export-quotation-marks
  as a utility function usable by individual exporters to apply
  `smart' quotes.

* contrib/lisp/org-e-latex.el: Replace org-e-latex-quotes custom with
  org-e-latex-quotes-replacements and make org-e-latex--quotation-marks
  use the org-export-quotation-marks function in org-export.el.

* contrib/lisp/org-e-html.el: Replace org-e-html-quotes custom with
  org-e-html-quotes-replacements and enable org-e-html--quotation-marks,
  using org-export-quotation-marks function in org-export.el.
---
 contrib/lisp/org-e-html.el  |   57 
 contrib/lisp/org-e-latex.el |   67 ++---
 contrib/lisp/org-export.el  |   26 +++
 lisp/org.el |  101 +++
 4 files changed, 168 insertions(+), 83 deletions(-)

diff --git a/contrib/lisp/org-e-html.el b/contrib/lisp/org-e-html.el
index 53547a0..d4a505e 100644
--- a/contrib/lisp/org-e-html.el
+++ b/contrib/lisp/org-e-html.el
@@ -1077,37 +1077,24 @@ in order to mimic default behaviour:
 
  Plain text
 
-(defcustom org-e-html-quotes
-  '(("fr"
- ("\\(\\s-\\|[[(]\\|^\\)\"" . "«~")
- ("\\(\\S-\\)\"" . "~»")
- ("\\(\\s-\\|(\\|^\\)'" . "'"))
-("en"
- ("\\(\\s-\\|[[(]\\|^\\)\"" . "``")
- ("\\(\\S-\\)\"" . "''")
- ("\\(\\s-\\|(\\|^\\)'" . "`")))
-  "Alist for quotes to use when converting english double-quotes.
-
-The CAR of each item in this alist is the language code.
-The CDR of each item in this alist is a list of three CONS:
-- the first CONS defines the opening quote;
-- the second CONS defines the closing quote;
-- the last CONS defines single quotes.
-
-For each item in a CONS, the first string is a regexp
-for allowed characters before/after the quote, the second
-string defines the replacement string for this quote."
+(defcustom org-e-html-smart-quote-replacements
+  '(("fr" "« " " »" "‘" "’" "’")
+("en" "“" "”" "‘" "’" "’")
+("de" "„" "“" "‚" "‘" "’"))
+  "What to export for `smart-quotes'.
+A list of five strings:
+ 1. Open double-quotes
+ 2. Close double-quotes
+ 3. Open single-quote
+ 4. Close single-quote
+ 5. Mid-word apostrophe"
   :group 'org-export-e-html
   :type '(list
-	  (cons :tag "Opening quote"
-		(string :tag "Regexp for char before")
-		(string :tag "Replacement quote "))
-	  (cons :tag "Closing quote"
-		(string :tag "Regexp for char after ")
-		(string :tag "Replacement quote "))
-	  (cons :tag "Single quote"
-		(string :tag "Regexp for char before")
-		(string :tag "Replacement quote "
+	  (string :tag "Open double-quotes"); "“"
+	  (string :tag "Close double-quotes")   ; "”"
+	  (string :tag "Open single-quote") ; "‘"
+	  (string :tag "Close single-quote"); "’"
+	  (string :tag "Mid-word apostrophe"))) ; "’"
 
  Compilation
 
@@ -1497,15 +1484,7 @@ This is used to choose a separator for constructs like \\verb."
   "Export quotation marks depending on language conventions.
 TEXT is a string containing quotation marks to be replaced.  INFO
 is a plist used as a communication channel."
-  (mapc (lambda(l)
-	  (let ((start 0))
-	(while (setq start (string-match (car l) text start))
-	  (let ((new-quote (concat (match-string 1 text) (cdr l
-		(setq text (replace-match new-quote  t t text))
-	(cdr (or (assoc (plist-get info :language) org-e-html-quotes)
-		 ;; Falls back on English.
-		 (as

Re: [O] Org, Org-mode, Orgmode, Org Mode

[François Pinard]

Hi, people.

On the nomenclature issue of our preferred tool, if I had my say, I
would suggest Org, and drop "mode".  Org is really a major Emacs mode,
in many acceptations of the word "major".  We should speak of Org the
same way we speak of Calc or Gnus (or Dired).

Of course, these all have a mode, and in fact, many of them, so we could
speak about Calc modes or Gnus modes, but Calc and Gnus (and Dired) are
just OK.  Same should go for Org, it is a grown up by now :-).

François

Re: [O] Local subtree view (analysis of a fundamental issue with subtree narrowing)

[Rebel Neurofog]

On Sun, Jun 3, 2012 at 6:51 AM, Samuel Wales  wrote:
> Hi Rebel,
>
> On 6/2/12, Rebel Neurofog  wrote:
>> The closest thing I'd like to have is (org-tree-to-indirect-buffer),
>> but, first, there's a bug in it (I use Emacs 23.4.2 - latest official):
>> - When I edit the last empty line in indirect buffer, the new text
>> gets into next entry (inside original buffer) like this:
>
>> ** TODO Go shoping
>> Some new text** TODO Finish Line Edit widget
>
> What version of Org are you running?  My version works.  That
> apparently empty line is possibly the beginning of the next line.  It
> might need a newline.  That is expected.

I've installed org-7.8.11
Now there's no flooding up of next line.
But original buffer is still edited incorrectly.

I even found org-indirect-buffer-display variable.
But still when I kill indirect buffer I have to press Tab several times
to make Org-mode specific things look fine.

I believe the problem is about indirect buffer editing:
modified part is inserted into view-precomposed data incorrectly.

Re: [O] Org, Org-mode, Orgmode, Org Mode

[Thorsten Jolitz]

François Pinard  writes:


> On the nomenclature issue of our preferred tool, if I had my say, I
> would suggest Org, and drop "mode".  Org is really a major Emacs mode,
> in many acceptations of the word "major".  We should speak of Org the
> same way we speak of Calc or Gnus (or Dired).

Org is nice, but:

,
| (Google)
| 
| org or "org"
| About 8,760,000,000 results
| 
| org-mode
| About 49,800,000 results   
| (but Org-mode on top)
| 
| org mode
| About 55,200,000 results   
| (but Org-mode on top)
| 
| "org-mode" or "org mode"
| About 812,000 results   
`

And isn't "org" often used as abbrev for "organisation" too?
Otherwise, Org sounds really good as a 'brand name'.
 

-- 
cheers,
Thorsten