Re: Structure templates moving point
Sorry, I didn't intend to keep digging. I would need to debug the buffer display behavior to find out why frames were being created to make a reproduction. The fallbacks I removed from `display-buffer-fallback-actions' were the ones that create frames. On Thu, Jun 6, 2024 at 7:18 PM Ihor Radchenko wrote: > Psionic K writes: > > > I made some changes to my buffer display settings. When the structure > > template choice interface does not fall back to creating a frame, it > > does not exhibit the errant point behavior. > > > > In any case, after creating the comment block, the point should > > probably move inside the block like it does for source blocks. > > Ok, but I cannot help without being able to reproduce the problem on my > side. Please provide detailed instructions how to reproduce the problem > starting from minimal Emacs config, as described on > https://orgmode.org/manual/Feedback.html#Feedback and > https://www.chiark.greenend.org.uk/~sgtatham/bugs.html > > -- > Ihor Radchenko // yantar92, > Org mode contributor, > Learn more about Org mode at <https://orgmode.org/>. > Support Org development at <https://liberapay.com/org-mode>, > or support my work at <https://liberapay.com/yantar92> > -- 남백호 대표 겸 공동 창업자 포지트론
Re: Structure templates moving point
I made some changes to my buffer display settings. When the structure template choice interface does not fall back to creating a frame, it does not exhibit the errant point behavior. In any case, after creating the comment block, the point should probably move inside the block like it does for source blocks.
Structure templates moving point
As of 9.7.2 Using `org-insert-structure-template' to add comment blocks to a document where I previously added comment blocks is moving the point to unrelated comments, and definitely not to the body of the block that was just inserted. The display buffer behavior is at least no longer creating frames I didn't want, but shouldn't it be a pop-up buffer? Likely to workaround by adding more snippets and disabling the command.
How should I handle babel configuration of exports & results in Dslide?
Because live presentations are a bit different from exporting documents, I'm not always sure how options should apply. I'm not an expert on many of these options and am not sure what will feel consistent for users. For context, a user wants :exports results or :exports none to hide the babel block / results. Issue is here: https://github.com/positron-solutions/dslide/issues/1 Is their idea consistent with the expectations and usages elsewhere? To implement options from the Dslide configuration, how can I explicitly change babel block behavior from an Elisp program? What function is best for cleaning up results of a single block? I'm using `org-babel-remove-result'. Whenever the babel args are :results replace, I am clearing them on that block both at the start fo the slide and when going backwards. Should this behavior interact with :exports? As you can see, feedback will be helpful in reconciling my understanding of the docs versus users actual expectations and common usage patterns. Thanks
dslide 0.4.0, last unstable release
Dslide (Domain Specific sLIDEs) is a rethought, mostly complete rewrite of org-tree-slide. Its highlight features: - using babel blocks - per-slide configuration - extensible via custom actions and support for custom EIEIO classes There is a file in the /test directory called demo.org. You can see the presentation with `dslide-deck-start' or `dslide-deck-develop' to watch progress updates be highlighted. You need my other package, `master-of-ceremonies' to complete the last slides of the presentation. https://github.com/positron-solutions/master-of-ceremonies There are a few areas I plan to change where feedback could be beneficial. Stop me if any of these choices seem unintuitive. I plan to get rid of the idea of independent `DSLIDE_SLIDE_ACTION' and `DSLIDE_SLIDE_CHILD_ACTION' and instead combine the child and slide behaviors into several distinct slide classes. The user will set `DSLIDE_CLASS` to achieve the combination of these two options. They will still accept plist style arguments for small behavior tweaks. Per-slide actions will still be supported, via `DSLIDE_EXTRA_ACTIONS' or `DSLIDE_ACTIONS' to completely override the normal actions set via customize or document properties. A user asked me to enable hiding babel blocks via setting the `:exports none`. I'm not sure if this is consistent with other uses of that option. My other option was to re-use the babel block keywords that are usually already present, adding just "hide" to the normal list of method names. You can reply directly if you like: https://github.com/positron-solutions/dslide/issues/1
Re: org-(un)fill-buffer
> smart fill prefix reliably. is that possible now? It's reasonably complete for several documents I'm converting, such as the transient showcase. Visual fill requires two modes right now: 1. visual-line-mode (usually with visual-fill-column-mode as well) 2. adaptive-wrap-prefix-mode Updating documents to this intended useage manner required an "unfill." I started off with the unfill package, which works by setting fill-column to most-positive-fixnum. Implementing an unfill buffer command uncovered the issue with fill-region in org mode. On Thu, Jan 11, 2024 at 10:12 AM Samuel Wales wrote: > > i lost track of all the visual fill stuff vs. emacs native filling vs. > org filling vs. filladapt back before visual filling was able to fill > with both a fill column and a reasonably smart fill prefix reliably. > is that possible now? > > also, if a new command is to be introduced, presumably it would work > on subtrees, paragraphs, lists, and regions, so that you could have it > not apply to informal non-org lists or code that is not in a source > block etc. > > met with alex today > yesterday he wasn't available > even thuogh he said he would be > > > On 1/10/24, Psionic K wrote: > > If I run fill-region on a buffer, there's a lot of errors where the > > lack of element awareness means filling is attempted on text that does > > not fill properly, such as property drawers, keywords, and even > > src-blocks without newline separations. The result requires way too > > much cleanup. > > > > It is critical to be able to unfill documents for people to migrate > > off of hard newlines and onto visual line mode with variable pitched > > fonts. > > > > I could probably convert this to a region-based command and we could > > shadow fill-region. It might be slightly tricky to deal with the > > region if it overlaps elements, but if I had to do it now, I would > > make the inclusion of part of an element include all of that element. > > > > On Thu, Jan 11, 2024 at 12:47 AM Ihor Radchenko > > wrote: > >> > >> Psionic K writes: > >> > >> >> You may instead just run > >> >> (let ((fill-column most-positive-fixnum)) (fill-region (point-min) > >> >> (point-max))) > >> > No. That will have to be run manually on every element and every line > >> > of every list. I suppose let's just not talk about it further and > >> > I'll submit a patch so there's no confusion. > >> > >> May you please elaborate what is wrong with `fill-region'? > >> > >> > This is the org-fill-buffer command, done generically for people who > >> > want > >> > to fill or unfill the entire buffer, as is required when alternating > >> > between hard newline filling and visual line mode filling. > >> > ... > >> > * lisp/org.el: (org-fill-buffer) this command walks the tree and will > >> > call fill-paragraph on every paragraph or plain-list element, enabling > >> > the user to quickly cycle between hard newlines or visual-line-mode. > >> > They can also adjust the fill, such as after removing indentation. > >> > >> I'd rather make use of the existing Emacs toggles that control filling, > >> so that `fill-region' works as expected. > >> > >> -- > >> Ihor Radchenko // yantar92, > >> Org mode contributor, > >> Learn more about Org mode at <https://orgmode.org/>. > >> Support Org development at <https://liberapay.com/org-mode>, > >> or support my work at <https://liberapay.com/yantar92> > > > > > > > > -- > > > > 남백호 > > 대표 겸 공동 창업자 > > 포지트론 > > > > > > > -- > The Kafka Pandemic > > A blog about science, health, human rights, and misopathy: > https://thekafkapandemic.blogspot.com -- 남백호 대표 겸 공동 창업자 포지트론
Re: org-(un)fill-buffer
If I run fill-region on a buffer, there's a lot of errors where the lack of element awareness means filling is attempted on text that does not fill properly, such as property drawers, keywords, and even src-blocks without newline separations. The result requires way too much cleanup. It is critical to be able to unfill documents for people to migrate off of hard newlines and onto visual line mode with variable pitched fonts. I could probably convert this to a region-based command and we could shadow fill-region. It might be slightly tricky to deal with the region if it overlaps elements, but if I had to do it now, I would make the inclusion of part of an element include all of that element. On Thu, Jan 11, 2024 at 12:47 AM Ihor Radchenko wrote: > > Psionic K writes: > > >> You may instead just run > >> (let ((fill-column most-positive-fixnum)) (fill-region (point-min) > >> (point-max))) > > No. That will have to be run manually on every element and every line > > of every list. I suppose let's just not talk about it further and > > I'll submit a patch so there's no confusion. > > May you please elaborate what is wrong with `fill-region'? > > > This is the org-fill-buffer command, done generically for people who want > > to fill or unfill the entire buffer, as is required when alternating > > between hard newline filling and visual line mode filling. > > ... > > * lisp/org.el: (org-fill-buffer) this command walks the tree and will > > call fill-paragraph on every paragraph or plain-list element, enabling > > the user to quickly cycle between hard newlines or visual-line-mode. > > They can also adjust the fill, such as after removing indentation. > > I'd rather make use of the existing Emacs toggles that control filling, > so that `fill-region' works as expected. > > -- > Ihor Radchenko // yantar92, > Org mode contributor, > Learn more about Org mode at <https://orgmode.org/>. > Support Org development at <https://liberapay.com/org-mode>, > or support my work at <https://liberapay.com/yantar92> -- 남백호 대표 겸 공동 창업자 포지트론
Re: org-(un)fill-buffer
This is the org-fill-buffer command, done generically for people who want to fill or unfill the entire buffer, as is required when alternating between hard newline filling and visual line mode filling. See attached patch for docstring and commit message. From 706d5d71cdf1ed2528664bdaf714aad6bd15af6c Mon Sep 17 00:00:00 2001 From: Psionik K <73710933+psioni...@users.noreply.github.com> Date: Wed, 10 Jan 2024 23:15:26 +0900 Subject: [PATCH] org.el: introducing org-fill-buffer * lisp/org.el: (org-fill-buffer) this command walks the tree and will call fill-paragraph on every paragraph or plain-list element, enabling the user to quickly cycle between hard newlines or visual-line-mode. They can also adjust the fill, such as after removing indentation. --- lisp/org.el | 32 1 file changed, 32 insertions(+) diff --git a/lisp/org.el b/lisp/org.el index 57379c26..1becc394 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -21901,6 +21901,38 @@ modified." (org-do-remove-indentation (funcall unindent-tree (org-element-contents parse-tree +(defun org-fill-buffer () + "Fill all paragraph and plain-list elements. +This command can be used to add hard newlines or to remove them. +To add hard newlines for text filling, set `fill-column' to the +desired with. To remove hard newlines, such as to prepare the +contents for `visual-line-mode', set `fill-column' to +`most-positive-fixnum'." + (interactive) + (unless (and (eq major-mode 'org-mode)) +(user-error "Cannot fill a buffer not in Org mode")) + (letrec ((parse-tree (org-element-parse-buffer 'greater-element nil 'defer)) + (fill-tree + (lambda (contents) + (dolist (element (reverse contents)) +(let ((type (org-element-type element))) + (if (member type '(headline section)) + (funcall fill-tree (org-element-contents element)) + (save-excursion + (save-restriction + (narrow-to-region + (org-element-begin element) + (org-element-end element)) +(goto-char (point-min)) +(pcase type + (`paragraph (fill-paragraph)) + (`plain-list + (mapc (lambda (i) + (goto-char (car i)) + (fill-paragraph)) +(reverse (org-list-struct) +(funcall fill-tree (org-element-contents parse-tree + (defun org-make-options-regexp (kwds &optional extra) "Make a regular expression for keyword lines. KWDS is a list of keywords, as strings. Optional argument EXTRA, -- 2.42.0
Re: org-(un)fill-buffer
> You may instead just run No. That will have to be run manually on every element and every line of every list. I suppose let's just not talk about it further and I'll submit a patch so there's no confusion. On Wed, Jan 10, 2024 at 9:31 PM Ihor Radchenko wrote: > > Psionic K writes: > > > I wrote up a small addition to the unfill package, which is very > > convenient for switching hard newlines out in favor of tools like > > visual-line-mode and adaptive-wrap. > > > > The command unfilled every list and paragraph in the entire buffer. PR is > > here: > > https://github.com/purcell/unfill/pull/11#pullrequestreview-1812645481 > > This PR introduces a function to "unfill" a region in Org mode buffer. > > > Steve wants to consider it for the org package itself. Questions from me: > > 1. will this be accepted? > > 2. where would it go? > > 3. because org is more general than unfill, I would instead name the > > command org-fill-buffer and we can recommend that users run in a hook: > > (setq-local fill-column most-positive-fixnum). After that, every call > > to `org-fill-buffer` will just do what they mean, just like how > > `fill-paragraph` will respect fill-column. > > You may instead just run > (let ((fill-column most-positive-fixnum)) (fill-region (point-min) > (point-max))) > > -- > Ihor Radchenko // yantar92, > Org mode contributor, > Learn more about Org mode at <https://orgmode.org/>. > Support Org development at <https://liberapay.com/org-mode>, > or support my work at <https://liberapay.com/yantar92> -- 남백호 대표 겸 공동 창업자 포지트론
Re: [PATCH] Unindentation fixup for code blocks
> Would you also be able to create a reproducer, so that we can replicate the problem and write a test? Yeah, I just have to make some indentation text invisible. Where should such a test live? Where is your documentation on running a test? > It looks like you did not send the patch with git send-emai. Nope. Magit patch create. Attaching another patch. > This math is not accurate when tabs are present. You want to short circuit this kind of conversation. I was not actually aware of any tabs versus spaces aware functions to build on top of since I always use spaces. Had I not already found another way to correct the behavior, this would have been a dead-end I would have had to round trip. I'm presuming tests don't get their own changelog entries. Is that correct? From 965b60f58512b009778b7b5279394bf01d407c3f Mon Sep 17 00:00:00 2001 From: Psionik K <73710933+psioni...@users.noreply.github.com> Date: Wed, 10 Jan 2024 22:37:28 +0900 Subject: [PATCH] org-macs.el: org-do-remove-indentation correction * lisp/org-macs.el (org-do-remove-indentation): set `buffer-invisibility-spec' to nil before detecting the column or moving to a column. This fixes src_block indentation removal for org-modern-mode but will also correct other cases of hidden indentation. --- lisp/org-macs.el | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lisp/org-macs.el b/lisp/org-macs.el index 8def5cbb..7f5d2ad8 100644 --- a/lisp/org-macs.el +++ b/lisp/org-macs.el @@ -408,7 +408,8 @@ line. Return nil if it fails." ;; Remove exactly N indentation, but give up if not possible. (when skip-fl (forward-line)) (while (not (eobp)) - (let ((ind (progn (skip-chars-forward " \t") (current-column + (let* ((buffer-invisibility-spec nil) + (ind (progn (skip-chars-forward " \t") (current-column (cond ((< ind n) (if (eolp) (delete-region (line-beginning-position) (point)) (throw :exit nil))) -- 2.42.0
org-(un)fill-buffer
I wrote up a small addition to the unfill package, which is very convenient for switching hard newlines out in favor of tools like visual-line-mode and adaptive-wrap. The command unfilled every list and paragraph in the entire buffer. PR is here: https://github.com/purcell/unfill/pull/11#pullrequestreview-1812645481 Steve wants to consider it for the org package itself. Questions from me: 1. will this be accepted? 2. where would it go? 3. because org is more general than unfill, I would instead name the command org-fill-buffer and we can recommend that users run in a hook: (setq-local fill-column most-positive-fixnum). After that, every call to `org-fill-buffer` will just do what they mean, just like how `fill-paragraph` will respect fill-column. I'm going to use the combination of `org-unindent-buffer` and `org-fill-buffer` in my own personal org shortcuts, but such a command is probably too much based on my personal taste. I think I will be recommending this combination to users in an upcoming video: 1. visual-fill-column 2. visual-line-mode 3. adaptive-wrap 4. configuring an org mode hook for "unfill" behavior 5. combining unindent with (un)fill in order to clean up old cruddy hard-indented, hard-newline documents
[PATCH] Unindentation fixup for code blocks
When cleaning up hard indentation, I found my source blocks remaining indented. The way that org-do-remove-indentation is sensitive to invisible text. This occurs for source blocks whenever using org-modern-mode, where it makes the source blocks align left. By swapping out the arithmetic and expressions that relied on current-column, the behavior is fixed. There are several behaviors I only just found, so I don't expect a lot of precision in my fix, but the patch I came up with follows: >From 858077f0d2a7f4cd8699948229c2965f0c6bb0a1 Mon Sep 17 00:00:00 2001 From: Psionik K <73710933+psioni...@users.noreply.github.com> Date: Wed, 10 Jan 2024 18:05:53 +0900 Subject: [PATCH] when removing indentation, take into account invisible text org-current-text-indentation sets invisibility spec to nil temporarily. One behavioral difference is that the point is no longer moved forward. Therefore, arithmetic is used instead of (current-column) based math. (current-column) is inaccurate when moving the point through invisible text. --- lisp/org-macs.el | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lisp/org-macs.el b/lisp/org-macs.el index 8def5cbb..0512cc48 100644 --- a/lisp/org-macs.el +++ b/lisp/org-macs.el @@ -408,13 +408,13 @@ line. Return nil if it fails." ;; Remove exactly N indentation, but give up if not possible. (when skip-fl (forward-line)) (while (not (eobp)) - (let ((ind (progn (skip-chars-forward " \t") (current-column + (let ((ind (org-current-text-indentation))) (cond ((< ind n) - (if (eolp) (delete-region (line-beginning-position) (point)) + (if (eolp) (delete-region (line-beginning-position) + (line-end-position)) (throw :exit nil))) (t (delete-region (line-beginning-position) -(progn (move-to-column n t) - (point) +(+ (line-beginning-position) n (forward-line))) ;; Signal success. t -- 2.42.0
Link translation & relative path export_file_name
When using an +#export_file_name directive, is it possible to have links translated to match the directory offset of the target? I came across this while working on a documentation generation scheme for https://github.com/positron-solutions/elisp-repo-kit The links in the org document are correct. The links in the resulting markdown are not translated, and break. The manual has a slightly different problem. I need to translate it as if it will be exported to the root directory even though it's always in the doc directory. The links don't seem useful, and turning them off may be more correct. I haven't gotten a lot of experience with drafting texinfo yet.
Re: Feature request: export form feed as page break
I am the original author of ox-odt.el. The page break feature is available as part of https://github.com/kjambunathan/org-mode-ox-odt This is a fork of the ODT exporter in Emacs Orgmode. If you are interested, please open an Discussions thread or a Issue on Github. Outline your requirements, and I will be happy to share a recipe or improve the ODT exporter. For those who rely on ODT exporter--I know there aren't many--please consider switching to my repo. If you are going to ask for a feature request for ODT exporter in emacs-orgmode, you can get some lip-service, and low-effort patches. (TLDR: The ODT exporter in Emacs is a working, but a dead code.) If you are going to ask for a feature request from me, you will actually see patches. (TLDR: I have been at this exporter for well over 13 years now. See my contribution activity on Github). As a PSA, I have been working on an experimental ODS export feature in order to help Uwe Brauer share Org mode tables (with TBLFMs) to ODS spreadsheet with Excel formulae. PS: ox-odt fork is a GPL software. (People who insist on licenses and go crazy about it are commercial minded, or ideological nuts. I am your neighbour uncle who wants to help you (and interact with you) in an unstructured setting ... Jambunathan K. On 21/10/23 13:12, Marvin Gülker wrote: Dear list, I am creating training material for the education of German law students, which usually consists of a case story on one or two pages, followed by a page break after which a proposal for resolving the case is provided. The structure is like this because usually I provide the case story before the meeting, where I work out a solution with the students, and afterwards I want to provide them with complete material, while still having everything contained in one file. With org, I can easily export to LaTeX and thereby to PDF, and it works quite nicely. However, for the page break I always need to write a literal \newpage into the document, which does work, but only in LaTeX. Since I am the only one using org/LaTeX at my chair, I have to convert these documents to DOCX (using the ODT exporter) when a collegue wants an editable version of them. As a LaTeX command, \newpage does not work when exporting to ODT. I thus open the exported document manually after the export and insert the page break using LibreOffice. To ease this process, I would like to request that the ASCII control character U+000C FORM FEED (displayed by emacs as ^L and also known as `\f' in C string notation) is recognised by exporters and translated to the corresponding page break command, that is, in LaTeX \newpage and in ODT to the XML that makes LibreOffice start a new page. For HTML, it could be exported as or similar, and for exporters which have no notion of pages, it could just be copied over to the exported document as-is. -MG
Re: [Pre-PATCH] Overhaul of the LaTeX preview system
Hello Timothy.
First of all, thank you for your contribution. I use your fork for some days
now and I can verify that it is working correctly. I have only faced the
following problems:
1. When a snippet contains a mistake, it correctly turns red, but no error
message
is shown when I hover my mouse over it. I have to switch to the *Org Preview
LaTeX Output*
to see the error.
2. Live previews do not work (like shown here https://tinyurl.com/5fu7z27w),
although
I am using the related options and use your branch up to the ---PATCH SET
DIVIDER--- commit.
3. When using your version, the ox-hugo exporter no longer works when latex is
involved.
The error that appears is the following:
org-html-format-latex: Invalid function: org-export-with-buffer-copy
4. Some key-binds (like C-c C-e to publish or C-c C-x C-l for latex-preview) do
not work
when the cursor is at the top of the file, before the first header.
In the attachments there are the diagnostics from the
org-latex-preview-check-health
function and my relevant configuration.
Again, thank you for this amazing overhaul and I hope it won't be long till
we see it merged in the official Org branch.
diagnostic-results
Description: Binary data
(setq org-latex-compiler "lualatex"
org-latex-preview-auto-generate 'live
org-latex-preview-persist nil
org-latex-preview-processing-indicator 'fringe
org-latex-preview-numbered t
org-latex-preview-width 0.75
org-latex-preview-use-precompilation nil
;; org-latex-preview-live-display-type 'eldoc
org-startup-with-latex-preview t
org-latex-preview-auto-generate t)
(setq org-latex-preview-preamble
"\\documentclass{article}
\\usepackage{amsmath}
\\usepackage{amssymb}
\\usepackage{amsfonts}
[DEFAULT-PACKAGES]
[PACKAGES]
\\usepackage{xcolor}")
;; \\usepackage{polyglossia}
;; \\setmainlanguage{greek}
;; \\setotherlanguage{english}
(plist-put org-format-latex-options :zoom 1.2) ; Calibrated based on the TeX font and org-buffer font.
(add-hook 'org-mode-hook #'org-latex-preview-auto-mode)
Re: [Pre-PATCH] Overhaul of the LaTeX preview system
Hello Timothy.
First of all, thank you for your contribution. I use your fork for some days
now and I can verify that it is working correctly. I have only faced the
following problems:
1. When a snippet contains a mistake, it correctly turns red, but no error
message
is shown when I hover my mouse over it. I have to switch to the *Org Preview
LaTeX Output*
to see the error.
2. Live previews do not work (like shown here https://tinyurl.com/5fu7z27w),
although
I am using the related options and use your branch up to the ---PATCH SET
DIVIDER--- commit.
3. When using your version, the ox-hugo exporter no longer works when latex is
involved.
The error that appears is the following:
org-html-format-latex: Invalid function: org-export-with-buffer-copy
4. Some key-binds (like C-c C-e to publish or C-c C-x C-l for latex-preview) do
not work
when the cursor is at the top of the file, before the first header.
In the attachments there are the diagnostics from the
org-latex-preview-check-health
function and my relevant configuration.
Again, thank you for this amazing overhaul and I hope it won't be long till
we see it merged in the official Org branch.(setq org-latex-compiler "lualatex"
org-latex-preview-auto-generate 'live
org-latex-preview-persist nil
org-latex-preview-processing-indicator 'fringe
org-latex-preview-numbered t
org-latex-preview-width 0.75
org-latex-preview-use-precompilation nil
;; org-latex-preview-live-display-type 'eldoc
org-startup-with-latex-preview t
org-latex-preview-auto-generate t)
(setq org-latex-preview-preamble
"\\documentclass{article}
\\usepackage{amsmath}
\\usepackage{amssymb}
\\usepackage{amsfonts}
[DEFAULT-PACKAGES]
[PACKAGES]
\\usepackage{xcolor}")
;; \\usepackage{polyglossia}
;; \\setmainlanguage{greek}
;; \\setotherlanguage{english}
(plist-put org-format-latex-options :zoom 1.2) ; Calibrated based on the TeX font and org-buffer font.
(add-hook 'org-mode-hook #'org-latex-preview-auto-mode)
diagnostic-results
Description: Binary data
Re: How to force markup without spaces
On Tue, 2022-07-26 at 13:30 +0700, Max Nikulin wrote:
> I have not tested it, but I expect you can use
> - export filter that removes zero-width spaces at the last export
> stage.
> I assume that your documents do not contain them besides markup
> workaround
> - #+latex_header: \DeclareUnicodeCharacter{200B}{}
> - custom link
>
> #+begin_src elisp :results none :exports both
> (org-link-set-parameters
>"sep"
>:export (lambda (path desc backend)
>(if (org-export-derived-backend-p backend 'org)
>(org-link-make-string (concat "sep:" path) desc)
> (or desc ""
> #+end_src
> "中文[[sep:][*测*]]试"
I tested the second workaround, and replaced the
\DeclareUnicodeCharacter{200B}{} sequence with \newunicodechar{}{} sequence
since I am using xelatex, which does not support the former.
It works fine so far.
> In other thread we are discussing advantages and problems of
> switching
> from PdfLaTeX to LuaLaTeX for non-latin scripts. The latter is a
> Unicode
> engine. I am curious what is your opinion from standpoint of Chinese
> language, namely amount of required customization in both cases. I
> think, it is better to either start a dedicated thread, or find the
> part
> of discussion related to fonts and babel (LaTeX package) setup.
As far as I know, Chinese users commonly use ctex package
https://ctan.org/pkg/ctex to handle Chinese typesetting problem, and they
prefer xelatex and lualatex over pdflatex. They don't support more fonts when
using pdflatex, compared with using xelatex etc. (you can see that on page 7 of
their pdf document). So I just use xelatex and don't have much experience using
pdflatex.
When using ctex, you just need to declare \documentclass{ctexart} (ctexart is a
ctex version article) to use Chinese characters. Then if your system has the
required default fonts, the pdf documents should be OK.
Re: How to force markup without spaces
On 2022-07-26 Tue. 09:23 +0700，Max Nikulin wrote： > However the suggestion was namely to use U+200B ZERO WIDTH SPACE and > it > is actually implemented since `org-emphasis-regexp-components' > currently > contains [:space:]. > ... > K, could you, please, clarify what is your particular use case? My bad, I misunderstood the "feature" mentioned in the old post. My use case is to emphasize chinese characters without spaces being inserted, even those zero-width spaces. For example "中文*测*试" should be enough to emphasize "测". I am using zero-width spaces right now, and it works fine in org-mode buffers, but if exported to latex-pdf files, the U+200B ZERO WIDTH SPACE character will not be zero-width for certain fonts. So I hope not to use that character. On Tue, 26 Jul 2022 09:26:42 +0800, Ihor Radchenko wrote: > Another idea we have discussed is using something similar to Markdown > format: **bold**, //italics//, __underline__, etc. It is less verbose > compared to the special blocks, which should be valuable for > Japanese/Chinese/other languages with no spaces between words. By the way, it seems that my use case has already been implemented by markdown-mode. In a markdown-mode buffer "中文**测**试" will certainly make "测" bold.
Re: How to force markup without spaces
Hello everyone, I am a chinese user and also came across this problem. Bastin once wrote this almost a decade ago: > More precisely this can be included when we decide to drop support > of Emacs 22. > > Does anyone know what is the current backward compatibility state > of major native Emacs packages (Gnus/ERC/etc) wrt Emacs 22? > > Thanks, > Since emacs has released 28.1, Could this problem be solved? Although we have the zero-width space workaround, for some fonts the character will not be zero-space. So it would be nice to solve this problem.
Re: How to force markup without spaces
> Bastin once wrote this almost a decade ago: Sorry for the misspelling, the name is Bastien, not Bastin. The thread and post I am mentioning is at https://list.orgmode.org/orgmode/87bodxy77m@bzg.ath.cx/
Re: How to force markup without spaces
Hello everyone, I am a chinese user and also came across this problem. Bastin once wrote this almost a decade ago: > More precisely this can be included when we decide to drop support > of Emacs 22. > > Does anyone know what is the current backward compatibility state > of major native Emacs packages (Gnus/ERC/etc) wrt Emacs 22? > > Thanks, > Since emacs has released 28.1, Could this problem be solved? Although we have the zero-width space workaround, for some fonts the character will not be zero-space. So it would be nice to solve this problem.
Bug: campany-capf throwing an error in org-mode, while entering header args [9.4.6 (9.4.6-12-gdcc3a8-elpaplus @ /home/mypc/.emacs.d/elpa/org-plus-contrib-20210809/)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
campany-capf throwing an error in org-mode, while entering header args
Error in `*Messages*` buffer
```
Company: backend company-capf error "Wrong type argument: char-or-string-p,
nil" with args (prefix)
```
Steps to reproduce
- emacs -Q
- `(add-to-list 'load-path "~/.emacs.d/elpa/company-20210811.214/")`
- `M-x load-library` `company`
- Open a org-mode buffer
- enable `company-mode`
- enter the example below, you will get the error when typing `:var`
```
#+Name: get-env
#+begin_src emacs-lisp
(print "hello")
#+end_src
#+begin_src emacs-lisp :var env=get-env()
(print env)
#+end_src
```
Expected behavior
This should not trigger an error.
The error backtrace
```
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
org-babel-balanced-split(nil 32)
#f(compiled-function (pair) #)((:var))
org-babel-parse-multiple-vars(((:var)))
org-babel-parse-header-arguments(":var" light)
#f(compiled-function (h) #)(":var")
org-babel-get-src-block-info(light)
pcomplete/org-mode/block-option/src()
pcomplete-completions()
pcomplete-completions-at-point()
completion--capf-wrapper(pcomplete-completions-at-point optimist)
company--capf-data-real()
company--capf-data()
company-capf(prefix)
apply(company-capf prefix)
company-call-backend-raw(prefix)
company--force-sync(company-call-backend-raw (prefix) company-capf)
company-call-backend(prefix)
company--continue()
company--perform()
company-post-command()
```
with `C-M-i` I get this error in messages buffer
```
Error in post-command-hook (completion-in-region--postch):
(wrong-type-argument char-or-string-p nil)
```
trace -
```
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
org-babel-balanced-split(nil 32)
#f(compiled-function (pair) #)((:var))
org-babel-parse-multiple-vars(((:var)))
org-babel-parse-header-arguments(":var" light)
#f(compiled-function (h) #)(":var")
org-babel-get-src-block-info(light)
pcomplete/org-mode/block-option/src()
pcomplete-completions()
pcomplete-completions-at-point()
completion--capf-wrapper(pcomplete-completions-at-point optimist)
company--capf-data-real()
company--capf-data()
company-capf(prefix)
apply(company-capf prefix)
company-call-backend-raw(prefix)
company--force-sync(company-call-backend-raw (prefix) company-capf)
company-call-backend(prefix)
company--begin-new()
company--perform()
company-auto-begin()
company-idle-begin(# # 230 95)
apply(company-idle-begin (# # 230
95))
timer-event-handler([t 24857 34109 966818 nil company-idle-begin
(# # 230 95) nil 848000])
```
Emacs : GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.20, cairo version 1.16.0)
of 2021-07-22
Package: Org mode version 9.4.6 (9.4.6-12-gdcc3a8-elpaplus @
/home/mypc/.emacs.d/elpa/org-plus-contrib-20210809/)
Re: Smart processing of http(s) links
Ag Ibragimov writes: > Oh cool. This is exactly what I needed: > > I was able to build this: > > #+begin_src emacs-lisp > (defun get-gh-item-title (uri &optional include-number?) > "Based on given github URI for (pull request or an issue), > returns its title" > (when (string-match "\\(github.com\\).*\\(issues\\|pull\\)" uri) ; either > PR or issue > (pcase-let* ((`(_ _ ,owner ,repo ,type ,number) (remove "" (split-string > uri "/"))) > (gh-resource (format "/repos/%s/%s/%s/%s" > owner > repo > (if (string= type "pull") "pulls" type) > number)) > (resp (ghub-get gh-resource nil :auth 'forge))) > (when resp > (format "%s%s" (alist-get 'title resp) > (when include-number? (format " #%s" number))) > > (defun org-link-make-description-function* (link desc) > (cond ((string-match "\\(github.com\\).*\\(issues\\|pull\\)" link) > (get-gh-item-title link :with-number)) > (t desc))) > > (setq org-link-make-description-function 'org-link-make-description-function*) > #+end_src > Thanks for this! > https://gist.github.com/agzam/b2f2d441acb96e1d693a2c81e9c4518f > On Sun 28 Jun 2020 at 14:02, Kyle Meyer wrote: > >> Ag Ibragimov writes: >> >>> Whenever I I use org-insert-link and it turns out to be a URI that >>> starts with "https://github.com"; I would like it to be processed >>> differently than any other link, one example - if it is a PR or a >>> Github Issue, I'd like it to fetch summary(title) of it and create a >>> link that looks like this: >>> >>> [[https://github.com/user/repo/issues/3899][This issue needs to be fixed >>> #3899]] >>> >>> Do we have any "built-in" mechanism for doing something like this? Can >>> someone suggest how I can make it. Thank you! >> >> You can set org-link-make-description-function to a function that >> detects links of interest and generates a custom description. > > -- Bonface M. K. (https://www.bonfacemunyoki.com) One Divine Emacs To Rule Them All GPG key = D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
[O] A summary with weekly processed actions using org-todo
Hi all, My life is relying on orgmode, from a personal standpoint (orgmode is faster at reminding me pending actions to fix my house than my wife) and to organize my actions at work pushing my mutt mails in org-mode as tasks... all this works great. Special thanks to the team for this superb work. I was wondering if there was a way to help me in sorting tasks. I have many actions/tasks during the week to process, some are done, some are waiting for feedbacks... on Mondays, I would like to generate a summary of the few actions that I changed the status during the last n-days (week, month...). I checked the Worg and other places but was not able to find the trick. I'm pretty sure somebody had this need before but am not able to find the answer. Thanks for your time ! Yann
Re: [O] C-c ! org-time-stamp-inactive ?
Nicolas Goaziou nicolasgoaziou.fr> writes: > > Hello, > > K limist.com> writes: > > > Kyle Meyer kyleam.com> writes: > > > >> > >> Hello, > >> > >> Luke Crook balooga.com> writes: > >> > >> > For me, C-c ! has suddenly become unbound and no longer inserts > >> > an inactive timestamp. Has this changed in the base org-mode, or > >> > most likely is this an issue with my setup? > >> > >> The default binding hasn't been changed in Org. > >> > > > > I've run into the same problem, with both Org 8.3.4 and MELPA version > > 20160307, the usual C-c ! doesn't work anymore for inserting inactive > > timestamp. If there's been no change to the default binding, any > > suggestions on how to debug this please? Thanks! > > What's the output of C-h c C-c ! in an Org buffer? > > Could you try with a minimal init file, just loading Org 8.3.4? > > Regards, > Hi Nicolas, Thanks for the suggestion. When I type C-h c C-c ! what I see is that it expects another character to be typed, it doesn't recognize C-c ! as complete/anything by itself. If I hit ENTER at that point, it shows, "C-c ! RET (translated from C-c ! ) is undefined" I tried starting Emacs with the -Q option, and of course C-c ! works as usual. I tried adding this line at the end of my personal customizations file: (define-key org-mode-map (kbd "C-c !") 'org-time-stamp-inactive) ...but it has no effect. What did work: C-h m and then search for !, showed that Flycheck mode uses that as its command prefix. Problem mostly solved, :-) K
Re: [O] C-c ! org-time-stamp-inactive ?
Kyle Meyer kyleam.com> writes: > > Hello, > > Luke Crook balooga.com> writes: > > > For me, C-c ! has suddenly become unbound and no longer inserts > > an inactive timestamp. Has this changed in the base org-mode, or > > most likely is this an issue with my setup? > > The default binding hasn't been changed in Org. > I've run into the same problem, with both Org 8.3.4 and MELPA version 20160307, the usual C-c ! doesn't work anymore for inserting inactive timestamp. If there's been no change to the default binding, any suggestions on how to debug this please? Thanks! K
Re: [O] Small bug? org-narrow-to-subtree and open file link
Igor Sosa Mayor gmail.com> writes: > > James K. Lin yahoo.com> writes: > > > org-narrow-to-subtree creates a subtree buffer. Your org-return call within > > that new subtree buffer command operates on the base buffer. Many of Org's > > link navigation commands operate this way because they use the base buffer > > as their context. > > thanks for your answer... I did not know about this... there is also > little to do? > > By default, Org mode does not work well with indirect buffers. You could get around this by rolling your own version of functions on your own to ignore the base buffer. This is no small feat because the link navigation commands are nested.
Re: [O] Small bug? org-narrow-to-subtree and open file link
Igor Sosa Mayor gmail.com> writes: > > Hi, > > maybe this is a small bug or something wrong in my config... > > But: if I use org-narrow-to-subtree and then use org-return to open a > file link the narrowed function get lost and I get the whole buffer > again. This happens at least if I get a question because the file is too > big and I have to decide whether I want to open it (this by the way > divides the window very unexpectedly...). > > I'm using Org-mode version 8.2.10. > > Any hint? > > Many thanks in advance! > > Igor, org-narrow-to-subtree creates a subtree buffer. Your org-return call within that new subtree buffer command operates on the base buffer. Many of Org's link navigation commands operate this way because they use the base buffer as their context.
Re: [O] emails written in Org Mode
Ken Mankoff writes: > Hi Thorsten, On a recent thread you wrote: > >> ... *outorg-edit-buffer* (where I write my message-mode email in full >> org-mode). > > I already write emails in emacs. I'm interested in being able to compose > emails using Org Mode. I see you use gnus. I use mu4e[1]. I wonder if > your setup is gnus-specific or might work with other emacs mail > clients. Will you provide some information about this? > Are you looking for something like this [1] ? Regards, Noorul [1] http://doc.norang.ca/org-mode.html#OrgStructModeForMail
Re: [O] [RFC] Creole-style / Support for **emphasis**__within__**a word**
Nicolas Goaziou writes: > Good luck. Got my answer. The rest are just details.
[O] ATTN: Users of ODT exporter
ATTN: Users of ODT exporter If you want to talk to me wrt exporter, please add a note here: http://www.emacswiki.org/emacs/Jambunathan_K I am leaving this list. I WILL NEVER MAKE an assignment to Emacs. i.e. The development that happens on my repository will NEVER hit the Emacs trunk.
Re: [O] Is anyone spending money for Org-mode?
If I were you, I will segregate the funds as though the contributor - developer or otherwise - will receive it. Then, I will approach each contributor with, This is your fair share. Please receive it. If the contributor declines, I will ask the contributor "How do you think I should deploy your fair share?" Carsten Dominik writes: > Hi all, > > one question that was asked: How much donations come in? That varies. > Some month it is $10, occasionally it can be $100. > > What Bastien and I have done in the past is use this money in a more > or less private way. I think Bastien has at some point replaced his > laptop in this way, and all in all I have done the same, I think. This > felt OK previously, but it is not longer the right thing as far as I > am concerned. > > I have seen a few good ideas here. > > 1. Send it to the FSF. That is a possibility, but lets first try to do > something more Org specific > > 2. A Mug for every contributor. Stretches the available budget, and is > work. > We could make a list of contributors and start from the most commits > or something. > > 3. Help organise a conference. That would be a very good goal. Are > there any plans to organise a conference? > > 4. Redistribute to the most active developers for lighting up their > day. > > I propose the following: Starting March 1, I will report here the > donations I get once a month, and we will keep track of it and find a > good way to spend it. So far this month: $66. Lets revisit the > discussion in 2 or three months. Maybe by then there will be plans for > a conference, if not, we see. > > - Carsten > > On Thu, Mar 13, 2014 at 8:55 PM, Eric Schulte > wrote: > > Here's an impractical option. I see roughly 280 different > contributors > to Org-mode. > > git log|grep "^Author"|sed 's/^.*: > //;s/<.*$//'|less|sort|uniq|less > > Maybe buy every contributor an Org-mode mug? > > -- > Eric Schulte > https://cs.unm.edu/~eschulte > PGP: 0x614CA05D > >
Re: [O] Is anyone spending money for Org-mode?
Carsten Dominik writes: > I would like to pass donations Undoubtedly, to Nicolas Goaziou.
Re: [O] FW: How to load .el file during startup and execute its commands (Win7/org8)
M writes: > have to load my settings file manually (open, eval-buffer, close) at > each startup... By hand, do M-x load-file RET path-to-file RET Now after you have done this, do M-x list-command-history RET And copy-paste the relevant portion to your .emacs. That is all. No need to mess with load-path. Here is what I get, when I follow the above sequence on one of my files. (load-file "~/.emacs.d/lisp/hx.el")
Re: [O] Howto: different faces for "begin_src" and "results"
Miguel Ruiz writes: > I was wondering if it's possible to have different faces for > "#+begin_src/#+end_src" and "results" so distinguishing the blocks is > easier. Put cursor on the character whose colour you want to change and do M-x cusotmize-face
Re: [O] org-odt-export-to-odt: tables: column and row spacing: configure
http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/txtXYCqBy8St9.txt Uwe Brauer writes: > Hello > > I use org-odt-export-to-odt quite a bit. How can I configure it in order > to set a different column and row spacing for tables? The default one is to > large > for my taste, > > Thanks > > Uwe Brauer
Re: [O] org-odt-export-to-odt: tables: column and row spacing: configure
If you want "optimized" column widths, I am afraid LibreOffice doesn't honor the XML markup. See http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg01203.html See http://lists.gnu.org/archive/html/emacs-orgmode/2014-02/msg00380.html Uwe Brauer writes: > Hello > > I use org-odt-export-to-odt quite a bit. How can I configure it in order > to set a different column and row spacing for tables? The default one is to > large > for my taste, > > Thanks > > Uwe Brauer
Re: [O] [RFC] Creole-style / Support for **emphasis**__within__**a word**
Jambunathan K writes: > (with-eval-after-load 'org > (setcar org-emphasis-regexp-components "^\\n") > (setcar (cdr org-emphasis-regexp-components) "^\\n") > (customize-save-variable 'org-emphasis-alist org-emphasis-alist)) A small correction Instead of \\n it should be \n. So use the below form instead. (with-eval-after-load 'org (setcar org-emphasis-regexp-components "^\n") (setcar (cdr org-emphasis-regexp-components) "^\n") (customize-save-variable 'org-emphasis-alist org-emphasis-alist))
[O] [RFC] Creole-style / Support for **emphasis**__within__**a word**
Nicolas
(Sorry for multiple posts. `customize-save-variable' in the attached
minimal emacs -- which I foolishly added to the top of my .emacs --
wiped out all my customizations including IMAP and SMTP settings)
[RFC] Creole-style / Support for **emphasis**__within__**a word**
The attached files should speak for themselves. Such an arrangement
a) Does not change the status quo AT ALL.
b) Provide more rope.
The patch is in the spirit of "show and tell". I will not provide a
formal patch.
What about formalizing such an arrangement...
#+OPTIONS: ':nil *:t -:t ::t <:t H:3 \n:nil ^:t arch:headline
#+OPTIONS: author:nil c:nil creator:comment d:(not "LOGBOOK") date:nil
#+OPTIONS: e:t email:nil f:t inline:t num:nil p:nil pri:nil prop:nil
#+OPTIONS: stat:t tags:t tasks:t tex:t timestamp:t toc:nil todo:t |:t
#+TITLE: a
#+DATE: <2014-03-04 Tue>
#+AUTHOR: Jambunathan K
#+EMAIL: kjambunathan@debian-6.05
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+SELECT_TAGS: export
#+EXCLUDE_TAGS: noexport
#+CREATOR: Emacs 24.3.50.33 (Org mode 8.2.5h)
Support for **emphasis**__within__**a word**. ==A proposal==.
* Headline 1
**bold**and**bold**//italic// __underline__==and==++strike-through++ plain text
emphasis.odt
Description: application/vnd.oasis.opendocument.text
.emacs.minimal.el
Description: application/emacs-lisp
diff --git a/lisp/org-element.el b/lisp/org-element.el
index 0faf1fd..131b442 100644
--- a/lisp/org-element.el
+++ b/lisp/org-element.el
@@ -2612,6 +2612,11 @@ Assume point is at the first star marker."
CONTENTS is the contents of the object."
(format "*%s*" contents))
+(defvar org-element--marker->type
+ (loop for markers in (mapcar 'car org-emphasis-alist)
+ for element-type in '(bold italic underline verbatim code strike-through)
+ collect (cons markers element-type)))
+
(defun org-element-text-markup-successor ()
"Search for the next text-markup object.
@@ -2622,15 +2627,10 @@ and CDR is beginning position."
(unless (bolp) (backward-char))
(when (re-search-forward org-emph-re nil t)
(let ((marker (match-string 3)))
- (cons (cond
- ((equal marker "*") 'bold)
- ((equal marker "/") 'italic)
- ((equal marker "_") 'underline)
- ((equal marker "+") 'strike-through)
- ((equal marker "~") 'code)
- ((equal marker "=") 'verbatim)
- (t (error "Unknown marker at %d" (match-beginning 3
- (match-beginning 2))
+ (cons
+ (or (assoc-default marker org-element--marker->type)
+ (error "Unknown marker at %d" (match-beginning 3)))
+ (match-beginning 2))
Code
diff --git a/lisp/org.el b/lisp/org.el
index f2bb99f..24f07f9 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -4191,10 +4191,14 @@ After a match, the match groups contain these elements:
(body (nth 3 e))
(nl (nth 4 e))
(body1 (concat body "*?"))
- (markers (mapconcat 'car org-emphasis-alist ""))
+ (markers (mapconcat (lambda (em)
+ (regexp-quote (car em))
+ )
+ org-emphasis-alist "\\|"))
(vmarkers (mapconcat
- (lambda (x) (if (eq (nth 2 x) 'verbatim) (car x) ""))
- org-emphasis-alist "")))
+ (lambda (x)
+ (regexp-quote (if (eq (nth 2 x) 'verbatim) (car x) "")))
+ org-emphasis-alist "\\|")))
;; make sure special characters appear at the right position in the class
(if (string-match "\\^" markers)
(setq markers (concat (replace-match "" t t markers) "^")))
@@ -4211,7 +4215,7 @@ After a match, the match groups contain these elements:
(setq org-emph-re
(concat "\\([" pre "]\\|^\\)"
"\\("
- "\\([" markers "]\\)"
+ "\\(" markers "\\)"
"\\("
"[^" border "]\\|"
"[^" border "]"
@@ -4223,7 +4227,7 @@ After a match, the match groups contain these elements:
(setq org-verbatim-re
(concat "\\([" pre "]\\|^\\)"
"\\("
- "\\([" vmarkers "]\\)"
+ "\\(" vmarkers "\\)"
"\\("
"[^" border "]\\|"
"[^" border "]"
[O] [RFC] Creole-style / Support for **emphasis**__within__**a word**
Nicolas
(Re-sent with the diff file)
[RFC] Creole-style / Support for **emphasis**__within__**a word**
The attached files should speak for themselves. Such an arrangement
a) Does not change the status quo AT ALL.
b) Provide more rope.
The patch is in the spirit of "show and tell".
That said, if I were to say "Let's formalize this arrangement" what will
you say?
#+OPTIONS: ':nil *:t -:t ::t <:t H:3 \n:nil ^:t arch:headline
#+OPTIONS: author:nil c:nil creator:comment d:(not "LOGBOOK") date:nil
#+OPTIONS: e:t email:nil f:t inline:t num:nil p:nil pri:nil prop:nil
#+OPTIONS: stat:t tags:t tasks:t tex:t timestamp:t toc:nil todo:t |:t
#+TITLE: a
#+DATE: <2014-03-04 Tue>
#+AUTHOR: Jambunathan K
#+EMAIL: kjambunathan@debian-6.05
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+SELECT_TAGS: export
#+EXCLUDE_TAGS: noexport
#+CREATOR: Emacs 24.3.50.33 (Org mode 8.2.5h)
Support for **emphasis**__within__**a word**. ==A proposal==.
* Headline 1
**bold**and**bold**//italic// __underline__==and==++strike-through++ plain text
emphasis.odt
Description: application/vnd.oasis.opendocument.text
.emacs.minimal.el
Description: application/emacs-lisp
diff --git a/lisp/org-element.el b/lisp/org-element.el
index 0faf1fd..131b442 100644
--- a/lisp/org-element.el
+++ b/lisp/org-element.el
@@ -2612,6 +2612,11 @@ Assume point is at the first star marker."
CONTENTS is the contents of the object."
(format "*%s*" contents))
+(defvar org-element--marker->type
+ (loop for markers in (mapcar 'car org-emphasis-alist)
+ for element-type in '(bold italic underline verbatim code strike-through)
+ collect (cons markers element-type)))
+
(defun org-element-text-markup-successor ()
"Search for the next text-markup object.
@@ -2622,15 +2627,10 @@ and CDR is beginning position."
(unless (bolp) (backward-char))
(when (re-search-forward org-emph-re nil t)
(let ((marker (match-string 3)))
- (cons (cond
- ((equal marker "*") 'bold)
- ((equal marker "/") 'italic)
- ((equal marker "_") 'underline)
- ((equal marker "+") 'strike-through)
- ((equal marker "~") 'code)
- ((equal marker "=") 'verbatim)
- (t (error "Unknown marker at %d" (match-beginning 3
- (match-beginning 2))
+ (cons
+ (or (assoc-default marker org-element--marker->type)
+ (error "Unknown marker at %d" (match-beginning 3)))
+ (match-beginning 2))
Code
diff --git a/lisp/org.el b/lisp/org.el
index f2bb99f..24f07f9 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -4191,10 +4191,14 @@ After a match, the match groups contain these elements:
(body (nth 3 e))
(nl (nth 4 e))
(body1 (concat body "*?"))
- (markers (mapconcat 'car org-emphasis-alist ""))
+ (markers (mapconcat (lambda (em)
+ (regexp-quote (car em))
+ )
+ org-emphasis-alist "\\|"))
(vmarkers (mapconcat
- (lambda (x) (if (eq (nth 2 x) 'verbatim) (car x) ""))
- org-emphasis-alist "")))
+ (lambda (x)
+ (regexp-quote (if (eq (nth 2 x) 'verbatim) (car x) "")))
+ org-emphasis-alist "\\|")))
;; make sure special characters appear at the right position in the class
(if (string-match "\\^" markers)
(setq markers (concat (replace-match "" t t markers) "^")))
@@ -4211,7 +4215,7 @@ After a match, the match groups contain these elements:
(setq org-emph-re
(concat "\\([" pre "]\\|^\\)"
"\\("
- "\\([" markers "]\\)"
+ "\\(" markers "\\)"
"\\("
"[^" border "]\\|"
"[^" border "]"
@@ -4223,7 +4227,7 @@ After a match, the match groups contain these elements:
(setq org-verbatim-re
(concat "\\([" pre "]\\|^\\)"
"\\("
- "\\([" vmarkers "]\\)"
+ "\\(" vmarkers "\\)"
"\\("
"[^" border "]\\|"
"[^" border "]"
[O] [RFC] Creole-style / Support for **emphasis**__within__**a word**
Nicolas [RFC] Creole-style / Support for **emphasis**__within__**a word** The attached files should speak for themselves. Such an arrangement a) Does not change the status quo AT ALL. b) Provide more rope. The patch is in the spirit of "show and tell". I will not provide a formal patch. That said, if I were to say "Let's formalize this arrangement" what will you say? .emacs.minimal.el Description: application/emacs-lisp emphasis.odt Description: application/vnd.oasis.opendocument.text #+OPTIONS: ':nil *:t -:t ::t <:t H:3 \n:nil ^:t arch:headline #+OPTIONS: author:nil c:nil creator:comment d:(not "LOGBOOK") date:nil #+OPTIONS: e:t email:nil f:t inline:t num:nil p:nil pri:nil prop:nil #+OPTIONS: stat:t tags:t tasks:t tex:t timestamp:t toc:nil todo:t |:t #+TITLE: a #+DATE: <2014-03-04 Tue> #+AUTHOR: Jambunathan K #+EMAIL: kjambunathan@debian-6.05 #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+SELECT_TAGS: export #+EXCLUDE_TAGS: noexport #+CREATOR: Emacs 24.3.50.33 (Org mode 8.2.5h) Support for **emphasis**__within__**a word**. ==A proposal==. * Headline 1 **bold**and**bold**//italic// __underline__==and==++strike-through++ plain text
Re: [O] Tables with line wrapping?
Peter Davis writes: > I'm using org-mode to prepare a document that will ultimately be > exported to PDF. Unfortunately, I need to include a table whose contents > will wrap as needed. You can export to PDF via ODT. Use list tables. See the links at the end of the following post. https://lists.gnu.org/archive/html/emacs-orgmode/2011-03/msg01101.html The list items (that you see below) is not limited to single lines but can be multi-line, multi-paragraph (including inline image links). The Hrules are optional. Some of the attributes you see below won't work on Org trunk but will work on my ELPA package. http://cauvery.nfshost.com/wiki.pl/ODT_Exporter --8<---cut here---start->8--- #+ATTR_ODT: :widths 1,2,4,8 #+ATTR_ODT: :rel-width 80 #+ATTR_ODT: :list-table t - - - Row 1 - 1.1 - 1.2 - 1.3 - - - Row 2 - 2.1 - 2.2 - 2.3 - - --8<---cut here---end--->8---
[O] bug#16734: Default value org-odt-data-dir (in Emacs) makes no sense
See these posts. http://permalink.gmane.org/gmane.emacs.orgmode/81330 http://permalink.gmane.org/gmane.emacs.orgmode/81364 If Org is run from Vanilla Emacs then setting then setting that to `org-odt-data-dir' to nil should work (I think). The primary consumer of `org-odt-data-dir' is a package distributor who distributes a STANDALONE org. He can set this variable to the location in the file system where he has dumped the styles file. >From the archives: http://lists.gnu.org/archive/html/emacs-orgmode/2012-01/msg00020.html Glenn Morris writes: > Package: emacs,org-mode > Version: 24.3.50 > > This refers to the version of Org mode in Emacs trunk. > > ./src/emacs -Q -l ox-odt > C-h v org-odt-data-dir > -> Its value is "/usr/share/emacs/etc/org" > > This value is hard-coded (and autoloaded; why?) in org-version.el. > This value makes no sense. > For Emacs, it should be something based on data-directory. > > This was pointed out before in some moderately lengthy discussion: > > http://lists.gnu.org/archive/html/emacs-devel/2012-10/msg2.html > http://lists.gnu.org/archive/html/emacs-devel/2012-10/msg00070.html > > (In general, the setting of directory-related variables in ox-odt seems > rather over-engineered.)
Re: [O] tricky odt export needs
Jambunathan K writes: > In the pdf version of Emacs info manuals one typically sees all three of > a Section number AND a Description AND a Page number, something like: > > See Section 3.1 [Tropical Storms], page 24. > > In Org context, I am wondering whether there is such a need. I have added support for generating page nos. See attachments for sample test file. --8<---cut here---start->8--- #+OPTIONS: ':nil *:t -:nil ::t <:t H:3 \n:nil ^:t arch:headline #+OPTIONS: author:t c:nil creator:comment d:(not "LOGBOOK") date:t #+OPTIONS: e:t email:nil f:t inline:t num:3 p:nil pri:nil prop:nil #+OPTIONS: stat:t tags:t tasks:t tex:t timestamp:t toc:t todo:t |:t #+TITLE: headline #+DATE: <2014-02-12 Wed> #+AUTHOR: Jambunathan K #+EMAIL: kjambunat...@gmail.com #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+SELECT_TAGS: export #+EXCLUDE_TAGS: noexport #+CREATOR: Emacs 24.3.50.20 (Org mode 8.2.5h) #+TOC: headlines * Headline 1 Some text. See [[Headline 2]]. #+PAGEBREAK: * Headline 2 Some more text. --8<---cut here---end--->8--- Page nos are disabled by default. To enable pagenos, you need to M-x customize-variable org-odt-caption-and-xref-settings and choose a setting as below. [X] Key: :TARGET: Plist: [X] Key: :xref-format Choice: Value Menu TexInfo style INS The "TexInfo style" is provided more for trial run. A variety of different "format strings" can be chosen. You can pull my changes from the following ELPA archive: http://repo.or.cz/w/org-mode/org-kjn.git/blob_plain/master:/ See instructions at http://cauvery.nfshost.com/wiki.pl/ODT_Exporter pagenos-after-upate.odt Description: application/vnd.oasis.opendocument.text pagenos.odt Description: application/vnd.oasis.opendocument.text #+OPTIONS: ':nil *:t -:nil ::t <:t H:3 \n:nil ^:t arch:headline #+OPTIONS: author:t c:nil creator:comment d:(not "LOGBOOK") date:t #+OPTIONS: e:t email:nil f:t inline:t num:3 p:nil pri:nil prop:nil #+OPTIONS: stat:t tags:t tasks:t tex:t timestamp:t toc:t todo:t |:t #+TITLE: headline #+DATE: <2014-02-12 Wed> #+AUTHOR: Jambunathan K #+EMAIL: kjambunat...@gmail.com #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+SELECT_TAGS: export #+EXCLUDE_TAGS: noexport #+CREATOR: Emacs 24.3.50.20 (Org mode 8.2.5h) #+TOC: headlines * Headline 1 Some text. See [[Headline 2]]. #+PAGEBREAK: * Headline 2 Some more text.
Re: [O] org-odt table with borders on all sides
rajat mukherjee writes: > org-odt table with borders on all sides Try one of this |---+---+---| | < | | > | | a | b | c | | d | e | f | | g | h | i | |---+---+---| or #+ATTR_ODT: :style "GriddedTable" | a | b | c | | d | e | f | | g | h | i | With the first version above, the vertical rules are indicated by "<" and ">" markers. The horizontal rules in the exported document will match the hrules in the table. If it doesn't work as expected in stock Org, try my package (which is documented at http://cauvery.nfshost.com/wiki.pl/ODT_Exporter)
Re: [O] export tables to html and odt, table borders
Uwe Brauer writes: > Is there anything similar for the odt exporter? 1. What SPECIFICALLY do you want? 2. How many tables do you have in your document? 3. What aspects do you want to be uniform across your tables? 4. What aspects you want changed on a per-table basis? If you want glosses or an all out gridded table, you need to start using the ELPA package or the use the :style "GriddedTable". See following posts: http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg01203.html http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg01088.html http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg01312.html
Re: [O] Need extra text in ODT export of headers
This is what I tried and I have LibreOffice 4.1.3.2 on Debian. See attachments for what I mean down below. 1. Export test.org to test.odt 2. Open test.odt, fix outline numbering and save as test.ott 3. Copy test.org to test-styled.org and apply test.ott as ODT_STYLES_FILE. 4. Export test-styled.org to test-styled.odt 5. I see that test-styled.odt has the required outline numbering. Don't be fooled by the numbering in TOC. The TOC is not in sync with what the style says. Just update the TOC (i.e., Update All) and everything will be just fine. I am assuming that what I show here - with some variations thereof - is what the OP wants to achieve. test-styled.odt Description: application/vnd.oasis.opendocument.text #+OPTIONS: ':nil *:t -:nil ::t <:t H:3 \n:nil ^:t arch:headline #+OPTIONS: author:t c:nil creator:comment d:(not "LOGBOOK") date:t #+OPTIONS: e:t email:nil f:t inline:t num:t p:nil pri:nil prop:nil #+OPTIONS: stat:t tags:t tasks:t tex:t timestamp:t toc:t todo:t |:t #+TITLE: test #+DATE: <2014-02-09 Sun> #+AUTHOR: Jambunathan K #+EMAIL: kjambunat...@gmail.com #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+SELECT_TAGS: export #+EXCLUDE_TAGS: noexport #+CREATOR: Emacs 24.3.50.20 (Org mode 8.2.5h) #+OPTIONS: tex:dvipng #+ODT_STYLES_FILE: "test.ott" * one ** two *** three test.ott Description: application/vnd.oasis.opendocument.text-template test.odt Description: application/vnd.oasis.opendocument.text #+OPTIONS: ':nil *:t -:nil ::t <:t H:3 \n:nil ^:t arch:headline #+OPTIONS: author:t c:nil creator:comment d:(not "LOGBOOK") date:t #+OPTIONS: e:t email:nil f:t inline:t num:t p:nil pri:nil prop:nil #+OPTIONS: stat:t tags:t tasks:t tex:t timestamp:t toc:t todo:t |:t #+TITLE: test #+DATE: <2014-02-09 Sun> #+AUTHOR: Jambunathan K #+EMAIL: kjambunat...@gmail.com #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+SELECT_TAGS: export #+EXCLUDE_TAGS: noexport #+CREATOR: Emacs 24.3.50.20 (Org mode 8.2.5h) * one ** two *** three Christian Moe writes: > Hi, Jambunathan, > > I was going to tell Dan the same thing, but for some reason, the below > doesn't work for me with outline numbering. Can you confirm that it > works for you? > > When I try, the paragraph styles from the template *do* get applied > (tested by coloring some headings), but the custom outline numbering > does not. > > To see if it ought to, I also tried to "load styles" from the OTT > into an ODT document, but again, custom outline numbering did not follow > along, so I'm not sure if it should be expected to work with Org ODT > export either. > > Yours, > Christian > > Jambunathan K writes: > >> The following message is a courtesy copy of an article >> that has been posted to gmane.emacs.orgmode as well. >> >> Dan Griswold writes: >> >>> The only downside right now seems to be that I have to do the outline >>> numbering for each file in the manuscript. But there are only 9 of >>> them. >> >> You just need to create a opendocument template file and have all the >> org file use it. >> >> See >> >>(info "(org) Applying custom styles") >> >> 1. Export ONE document. >> 2. Fix outline numbering >> 3. Save the file as say custom-style.ott (Note: It is OTT and not ODT) >> 4. Add a directive to ALL THE OTHER org file as below. >> >>M-x org-export-insert-default-template odt >> >>and modify the ODT_STYLES_FILE directive as below. >> >> #+ODT_STYLES_FILE: "~/a/b/custom-style.ott" >> >> 5. Now if I export the org files with (4), you will get the outline >>numbering that you desire.
Re: [O] Need extra text in ODT export of headers
Dan Griswold writes: > The only downside right now seems to be that I have to do the outline > numbering for each file in the manuscript. But there are only 9 of > them. You just need to create a opendocument template file and have all the org file use it. See (info "(org) Applying custom styles") 1. Export ONE document. 2. Fix outline numbering 3. Save the file as say custom-style.ott (Note: It is OTT and not ODT) 4. Add a directive to ALL THE OTHER org file as below. M-x org-export-insert-default-template odt and modify the ODT_STYLES_FILE directive as below. #+ODT_STYLES_FILE: "~/a/b/custom-style.ott" 5. Now if I export the org files with (4), you will get the outline numbering that you desire.
Re: [O] [ANN] ELPA package for ODT and JabRef exporters
Aric Gregson writes: > Jambunathan, > > I have tried to install this. I even created a blank .emacs file as you > suggested. Everything appears to be fine with the exception of > >>C-h v org-odt-styles-dir >>C-h v org-odt-schema-dir > > These do not appear as options for me. I'm not sure if that matters. Most likely that ODT backend is not loaded. Try this. 1. Configure org-export-backends and add ODT to it. 2. Put (setq org-odt-data-dir nil) at the start of Emacs. 3. Visit an Org file and export to ODT Now check the *Messages* buffer and the value of the above variables. > Thanks, Aric
[O] [bug] Code snippets are not getting numbered
Nicolas Code snippets are not getting numbered... Also take a look at `org-export-resolve-coderef'. The below example is from (info "(org) Literal examples") --8<---cut here---start->8--- #+BEGIN_SRC emacs-lisp -n -r (save-excursion (ref:sc) (goto-char (point-min)) (ref:jump) #+END_SRC In line [[(sc)]] we remember the current position. [[(jump)][Line (jump)]] jumps to point-min. --8<---cut here---end--->8---
Re: [O] No title in org-export-as-odt
Brady Trainor writes: > Miguel Ruiz yahoo.es> writes: > >> > > Any hint to get rid of the title in a org-export-as-odt If you are seeing `org-export-as-odt' then you are using old Org (< 8.0). Old exporters are no longer maintained. So you upgrade to the latest Org (org > 8.0) via M-x list-packages. Btw, I have a provided a fix as part of my ELPA package[fn:1]. If #+TITLE: is made of just whitespaces, the exported document will no longer have the corresponding fieldnames. [fn:1] http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg01312.html
Re: [O] Which `odt-content' variable should I use? Why are there two?
Brady Trainor writes: > I was browsing the customize group org-export-odt. The old exporter and the new exporters share the same custom group. So you are seeing the old and new variables in the custom buffer. (IMO this is a bug.) NEW variables do NOT have an extra "export" in their names == If you are using org > 8.0, the variables that you are interested in should come from ox-odt.el. M-x find-library ox-odt M-< C-s defcustom (defcustom org-odt-prettify-xml nil ^^^ (defcustom org-odt-schema-dir ^^^ Note that NEW variables don't have "export" in their names. Except for change in the prefix, the functionality is for most part the same. Migrate: Use search and replace So, a simple renaming in your .emacs should suffice for migrating your old settings to the new settings. C-x C-f .emacs M-% org-export-odt- org-odt- C-x C-s
Re: [O] [ANN] ELPA package for ODT and JabRef exporters
This message SUPERSEDES instructions in the parent post (at
http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg01134.html)
Elevator Pitch
==
I fixed few bugs in ELPA tarball (Thanks Benjamin). Adding the
following URL to
http://repo.or.cz/w/org-mode/org-kjn.git/blob_plain/master:/
to
C-h v package-archives
should work now.
WARNING: Don't forget the trailing "/" in the above URL.
ELPA tar for ODT + JabRef
=
I have prepared an ELPA package
org-odt-*.tar
for easy distribution of bug fixes from private git repository [fn:1].
The package contains both ODT exporter and JabRef exporter. It also
contains a standalone documentation (in both info and pdf format) for
the ODT exporter.
Pre-Requisites
==
Before installing the ODT tarball please ensure that you are using
1. org > 8.0
2. Emacs > 24.3.50
A good way to find out if you are running org > 8.0 is to do this:
M-x locate-library ox
If you get a hit, then you are using org > 8.0.
If you don't find ox.el, you need to upgrade to org > 8.0. The best way
to upgrade to the most recent org is via package manager (i.e., M-x
list-packages)
Steps for installing ODT + JabRef ELPA package
=
1. Clear out your .emacs. (Not needed, if you know what you are doing)
2. Ensure that you are using org > 8.0 (See previous instructions)
3. Update your package archives to include the "org-odt" repo.
(custom-set-variables
'(package-archives
(quote
(("gnu" . "http://elpa.gnu.org/packages/";)
("org-odt"
. "http://repo.or.cz/w/org-mode/org-kjn.git/blob_plain/master:/";)
4. Now do
M-x list-packages
Look out for "org-odt" package. Install it.
5. Goto start of .emacs and add the following line. (This should be the
FIRST LINE in your .emacs)
(setq org-odt-data-dir nil)
6. Check ON the ODT option under
M-x customize-variable RET org-export-backends RET
7. Restart Emacs
8. Make sure that the following commands point to the ELPA directory
M-x locate-library RET ox-odt RET
M-x locate-library RET ox-jabref RET
C-h v org-odt-styles-dir
C-h v org-odt-schema-dir
9. Visit test.org and export it. Enjoy.
Some existing gotchas and bugs wrt `org-odt-data-dir'
=
(5) above is needed to work around a bug in Emacs snapshot and Org build
system.
How to host the above files on your own ELPA server
==
If someone wants to distribute the above files, please put the following
files in your web-server.
1. Copy org-odt-MMDD.tar
2. Copy archive-contents
Hint for ELPA Hosting
==
See directory structure of http://orgmode.org/elpa/
1. Various tar files are under that directory.
2. archive-contents points to the very LATEST tar file.
http://orgmode.org/elpa/archive-contents
ODT exporter and Copyright Issues and a Note to the Users
=
[fn:1] http://repo.or.cz/w/org-mode/org-kjn.git
The above repo. contains many bug-fixes and enhancements that are NOT
available with Emacs-24.4 or Orgmode git repo.
For some reasons, emacs-devel, Org developers and I don't meet eye to
eye. See
http://lists.gnu.org/archive/html/emacs-devel/2013-12/msg00509.html. So
the enhancements that are distributed with the above archive are
unlikely to be avaible with Emacs or Org git repo.
To the people who rely on ODT exporter for their day to day use and want
it as part of Emacs
1. Find someone with Copyright Assignment to fix the critical issue(s).
2. Write to Gnu/Linux distributors - Debian, Gentoo etc - and persuade
them to apply patches from my private repo before building the
org-mode or Emacs deb packages.
Note to Org developers
==
If anyone comes this far, let me note that Bastien's latest change to
ox-odt.el resembles very much fix on my Org private repo. I would argue
that this fix borrows "very liberally" from my un-assigned changes. So
.
Re: [O] Aligned glosses in orgmode (for export to odt/doc)
Jambunathan K writes: > Benjamin Slade writes: > >> One potential solution would be an orgmode setup which produces >> borderless tables with an "optimal width" column setting. I don't know >> how to do this in orgmode though (or if it can be done currently). In Office XML, the style:table-column-properties has style:use-optimal-column-width="true". Based on my little experimentation, I find that LibreOffice doesn't honor this setting. This is the reason why columns are emitted unoptimized. >From LibreOffice UI, if you choose "Optimal Column Width", then the table columns are emitted NOT with above XML attribute but with hard-coded on-the-fly widths. May be someone can take the above issue with LibreOffice folks... > 2. Open OrgOdtContentTemplate.xml and find a style named > "CustomTableCell". Edit it so that it has no borders. Ignore the above suggestion. It is too tedious. I have flushed out a fix as part of the following ELPA tar http://repo.or.cz/w/org-mode/org-kjn.git/blob_plain/master:/org-odt-20140124.tar With this fix, the behaviour of the rules in the ODT table will be much the same as that in (info "(org) Tables in ODT export") except for the following modification: The ODT table will have top rule (or bottom rule) only if the Org-mode table has one. Similarly, ODT table will have left rule (resp. right rule) only if the leftmost (resp. rightmost) data column has "<" and ">" markers. To cut the long story short, here is how you produce a borderless table. Use the :widths and :rel-width property to have the table look compact and nice. --8<---cut here---start->8--- This table has no rules. It occupies 80% of page width. The columns will be in the ratio of 4:7:10. #+ATTR_ODT: :rel-width 80 #+ATTR_ODT: :widths 3,6,9 | a | b | c | | d | e | f | --8<---cut here---end--->8--- test.odt Description: application/vnd.oasis.opendocument.text
Re: [O] odt exporter on mixed org setup
Achim Gratz writes: > That's the result of using Emacs' build system, not Org's. Someone has to fix it... It should either be nil or (expand-file-name "./org/" data-directory) If that path is wrong, the ODT exporter is really not usable. I think nil may be a good idea.
Re: [O] Citations and references in ODT
Jambunathan K writes: > Try out the org-odt-* ELPA package and let me know how things go. See http://permalink.gmane.org/gmane.emacs.orgmode/81347
Re: [O] Citations and references in ODT
Try out the org-odt-* ELPA package and let me know how things go. Aric Gregson writes: > --On January 19, 2014 11:16:53 AM +0530 Jambunathan K > wrote: > >> Are you still stuck here or you made some repairs and stuck elsewhere. > ... >> IMO, starting from scratch (i.e., an empty .emacs) and installing Org >> via M-x list-packages is a sure way to have a working setup with minimal >> fuss. > > Yes, still stuck here. All works fine so long as I don't try to use > your modified files, thus I imagined it was due to some error when > installing your modified files for org, which it must be. I will look > through and reinstall again and see what I can find. Otherwise, works > well enough now without the ox-jabref.el. > Aric
Re: [O] Aligned glosses in orgmode (for export to odt/doc)
Benjamin Slade writes: > Can anyone suggest how this (or some other solution to producing > interlinear glosses) might be implemented in an orgmode->odt/doc/docx > setup? One potential solution would be an orgmode setup which produces > borderless tables with an "optimal width" column setting. I don't know > how to do this in orgmode though (or if it can be done currently). Feel free to use my ELPA package. I have documented the procedure here http://permalink.gmane.org/gmane.emacs.orgmode/81347 Going forward, I will release my packages - ox-odt and org-jabref - via ELPA tarball. So, ELPA installation will be the recommended method for accessing my private package. You can ignore my earlier message at: http://permalink.gmane.org/gmane.emacs.orgmode/81301
[O] [ANN] ELPA package for ODT and JabRef exporters
I have prepared an ELPA package
org-odt-*.tar
for easy distribution of bug fixes from private git repository [fn:1].
The package contains both ODT exporter and JabRef exporter. You need to
make sure that you are using
1. org > 8.0
2. Emacs > 24.3.50
Steps for installing ODT + JabRef ELPA package
=
1. Clear out your .emacs. (Not needed, if you know what you are doing)
2. Visit http://repo.or.cz/w/org-mode/org-kjn.git/tree/master and
download the a tar file named org-odt-MMDD.tar. (Click on the
"raw" link)
As of now, the file is available at:
http://repo.or.cz/w/org-mode/org-kjn.git/blob_plain/master:/org-odt-20140123.tar
3. M-x package-install-file RET RET
4. Goto start of .emacs and add the following line. (It should be the
first line in your .emacs)
(setq org-odt-data-dir nil)
5. Check the ODT option under
M-x customize-variable RET org-export-backends RET
6. Restart Emacs
7. Make sure that the following commands point to the ELPA directory
M-x locate-library RET ox-odt RET
M-x locate-library RET ox-jabref RET
C-h v org-odt-styles-dir
C-h v org-odt-schema-dir
8. Visit test.org and export it. Enjoy.
Some existing gotchas and bugs
=
(4) above is needed to work around a bug in Emacs snapshot and Org build
system.
Wrt (2) and (3), I would have expected that the following
(custom-set-variables
'(package-archives
(quote
(("gnu" . "http://elpa.gnu.org/packages/";)
("org-odt"
. "http://repo.or.cz/w/org-mode/org-kjn.git/blob_plain/master:/";)
would suffice to do install via
M-x list-packages.
Unfortunately for some reasons package.el refuses to download the
"archive-contents" located at
http://repo.or.cz/w/org-mode/org-kjn.git/blob_plain/master:/archive-contents.
Any one interested in investigating this and if necessary file a bug
report against Emacs.
How to host the above files on your own ELPA server
==
If someone wants to distribute the above files, please put the following
files in your web-server.
1. Copy org-odt-MMDD.tar
2. Copy archive-contents
See directory structure of http://orgmode.org/elpa/
1. Various tar files are under that directory.
2. archive-contents points to the very latest tar file.
http://orgmode.org/elpa/archive-contents
ODT exporter and Copyright Issues and a Note to the Users
=
[fn:1] http://repo.or.cz/w/org-mode/org-kjn.git
The above repo. contains many bug-fixes and enhancements that are NOT
available with Emacs-24.4 or Orgmode git repo.
For some reasons, emacs-devel, org developers and I don't meet eye to
eye. See
http://lists.gnu.org/archive/html/emacs-devel/2013-12/msg00509.html. So
the above fixes are unlikely to be avaible with Emacs or Org git repo.
To the people who rely on ODT exporter for their day to day use and want
it as part of Emacs
1. Find someone with Copyright Assignment to fix the critical issue(s).
2. Write to Gnu/Linux distributors - Debian, Gentoo etc - and persuade
them to apply patches from my private repo before building the
org-mode or Emacs deb packages.
Note to Org developers
==
If anyone comes this far, let me note that Bastien's latest change to
ox-odt.el resembles very much fix on my Org private repo. I would argue
that this fix borrows "very liberally" from my un-assigned changes. So
.
Re: [O] Including Tables and Figures in TOC for org-odt-export
Rajat Mukherjee writes: > Hello Org-mode users, > Can any body direct me as to how to include list of tables and figures in the > toc when exporting to odt from orgmode. Org cannot generate TOC of tables and figures. You need to use LibreOffice to insert Index of Table and Figures (by hand). You are the first user to ask for this feature. If I see more people shouting out for this feature, I can consider adding it. > Many thanks in advance, > Rajat.
Re: [O] odt exporter on mixed org setup
Achim Gratz writes: > Bzzt. Wrong. I have my reservations. With stock Emacs Snapshot (i.e., without any separate Org installation - git or elpa) at Bzr version 116124, at line 16, I am seeing ;;;###autoload (defvar org-odt-data-dir "/usr/share/emacs/etc/org" "The location of ODT styles.") I hard-coded path, on a platform-independent file, makes me cringe?
Re: [O] Aligned glosses in orgmode (for export to odt/doc)
Benjamin Slade writes:
> One potential solution would be an orgmode setup which produces
> borderless tables with an "optimal width" column setting. I don't know
> how to do this in orgmode though (or if it can be done currently).
This feature is available only in my private repo.
If you are using Git see instructions at:
http://lists.gnu.org/archive/html/emacs-orgmode/2013-12/msg00522.html
(Search for "Download")
Once you download and copy the ox-odt.el file, make sure you do
M-x byte-compile-file
to create .elc file.
If you are using ELPA see instructions at:
http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg00518.html
(Search for "Untar")
1. Identity where your styles files come from. Look at the *Messages*
buffer for clue.
2. Open OrgOdtContentTemplate.xml and find a style named
"CustomTableCell". Edit it so that it has no borders.
Replace this
with this:
3. Create a tables as below. ("GriddedTable" is part of C-h v
`org-odt-table-styles'). WARNING: Don't try to understand the
documentation. I don't it understand it myself.
--8<---cut here---start->8---
Rows will be in the ratio of 2:3:4
#+ATTR_ODT: :style "GriddedTable"
| <1> | <2> | <3> |
| _a_ | _b_ | _c_ |
| _d_ | _e_ | _f_ |
Rows will be in the ratio of 4:7:10. Table will occupy 80% of page width.
#+ATTR_ODT: :rel-width 80
#+ATTR_ODT: :widths 3,6,9
#+ATTR_ODT: :style "GriddedTable"
| <1> | <2> | <3> |
| _a_ | _b_ | _c_ |
| _d_ | _e_ | _f_ |
--8<---cut here---end--->8---
4. Export it. You will get the attached ODT file.
test.odt
Description: application/vnd.oasis.opendocument.text
Re: [O] orgstruct-mode taking over C-c C-f
Eric Abrahamsen writes: > Debugger entered--Lisp error: (void-function set-transient-map) New function in snapshot builds. ChangeLog says 2013-12-23 Chong Yidong * subr.el (set-transient-map): Rename from set-temporary-overlay-map. Doc fix.
Re: [O] orgstruct-mode taking over C-c C-f
Eric Abrahamsen writes: > Debugger entered--Lisp error: (void-function set-transient-map) New function in snapshot builds. From the ChangeLog 2013-12-23 Chong Yidong * subr.el (set-transient-map): Rename from set-temporary-overlay-map. Doc fix.
Re: [O] How to write medical journal articles with org-mode
regcl writes: > org > latex > pandoc > docx ? Too many moving parts. Each part coming from different manufacturers. The components will rub against each other and the resulting heat may vaporize the lubricant. Pick a workflow that has minimum dependencies - even if that means throwing Emacs out the Windows.
Re: [O] How to write medical journal articles with org-mode
regcl writes: > I am looking for advice regarding how to write medical journal > articles using org-mode. > > My primary motivations are the desire to ... automate the flow of data > from computation to publication, avoid clerical errors, speed up the > conversion of computational results to manuscript, and do 99.9% of my > typing in emacs ;) > > My primary computation platform is linux clusters with OS X desktops. > I have used org-mode for project management and HTML export of > provisional computational results in working papers for ~1 year. > > I recently started using org-mode/babel/ESS/R to export computation > results to HTML. > > It looks like the medical journals require MS word submissions. I > have used the scheme shown below to get MSword to/from my > collaborators for comments & corrections ... > > doc.org--+ > || > v| > M-x org-odt-export-to-odt| > || > v| > Open office | > || > v| > MS Word | > || > v| > doc.docx | > || > v| You can do it in a single step with `org-odt-preferred-output-format'. See (info "(org) Extending ODT export"). > 1) Has anyone out there used org-mode to produce medical journal > articles (other than demonstration of reproducible research)? > 3) How do I get references into MS word? You can use ODT Export with JabRef using ox-jabref.el. You may want to check whether the JabRef project has layout files that can create citations in a format acceptable to Medical Journals. (Search the list reverse chronologically.)
Re: [O] Citations and references in ODT
Aric Gregson writes: > From http://permalink.gmane.org/gmane.emacs.orgmode/80832 > OpenDocument export failed: Symbol's function definition is void: > org-element-cache-reset > I also receive this error the first time that I try to open an org > file. I can open the file if I try another time. Are you still stuck here or you made some repairs and stuck elsewhere. The above error has nothing to do ox-odt.el or ox-jabref.el. It says your org-element.el is coming from some unexpected path. The problem is usually because of wrong installation. > Jambunathan has any ideas as to why his exporter is not working with my > set-up. It is difficult for me to imagine how you set up things. (There are so many moving parts). All I can say is this: "Not related to odt/jabref exporters. Something is related to how you have setup things". Nothing more. You will have better luck if 1. You start emacs with a blank .emacs 2. Install Org from ELPA. Once you have a working ox-odt.el setup, then you can make additional modifications to that setup and install ox-jabref.el. Your best debug tools are 1. M-x find-library 2. M-x locate-library 3. M-x list-load-path-shadows. You can run the above commands vis-a-vis the following libraries 1. org-loaddefs 2. org-compat 3. org-element.el and investigate *for yourself* whether the paths are getting "mixed up". If you analyse the output, you will understand what I mean. Most likely there are stale or non-existent .elc files or the .elc files were generated against a stale library. IMO, starting from scratch (i.e., an empty .emacs) and installing Org via M-x list-packages is a sure way to have a working setup with minimal fuss.
Re: [O] odt exporter on mixed org setup
Rustom Mody writes: > On second thoughts Added few more lines, Sundays after Harvest season are the best :-) Don't disturb it So long as it works Scribble the notes somewhere Tuck it in a safe place So that, When times are bad And things go awry Revisit the memories (And) Things are right again Still if, Things are beyond repair Or gears rusted Shout out my name From the darkest corridors Will come a repair-man.
Re: [O] odt exporter on mixed org setup
Rustom Mody writes: > On second thoughts Don't disturb it So long as it works Scribble the notes somewhere Tuck it in a safe place (So that) When times are bad And things go awry Revisit the memories (And) Set things right again.
Re: [O] odt exporter on mixed org setup
Rustom Mody writes: > Currently I have a setq on org-mode-hook I don't run "make install", I just do "make". Here is what I have in .emacs. DO NOT do an explicit (require 'ox-backend). Instead customize `org-export-backends' and the ODT exporter there. Here is the sequence I have in my .emacs. (add-to-list 'load-path "~/src/org-mode/lisp/") (require 'org-loaddefs) (add-to-list 'load-path "~/src/org-mode/contrib/lisp/") (setq org-odt-data-dir "~/src/org-mode/etc/") (custom-set-variables '(org-export-backends (quote (ascii html icalendar latex odt org)))
Re: [O] odt exporter on mixed org setup
Rustom Mody writes: > org-odt-data-dir is coming in bound to /usr/share/emacs/etc/org (which > is non-existent) Open a bug against the packager. (ox-odt.el is an exception. It is uncommon for Emacs libraries to come with auxiliary support files). The distributors need to make sure 1. Style files are bundled correctly. 2. `org-odt-data-dir' is configured to point to (1). I don't know much about the build system.
Re: [O] odt exporter on mixed org setup
Rustom Mody writes: > I could check that org-odt-data-dir is coming in bound to > /usr/share/emacs/etc/org (which is non-existent) before the defvar in > ox-odt.el, so that defvar is not happening > And changing the prefix in local.mk does not seem to do anything Don't worry about the make file. (It is difficult for the make file to cater to different distributions, different installations - git, release tar file etc) The most easiest setup will be ELPA or using ox-odt that ships with Emacs proper.
Re: [O] odt exporter on mixed org setup
Rustom Mody writes: > Ended with: ox-odt cannot find factory style files You need (setq org-odt-data-dir "~/src/org-mode/etc/") Modify the path. If the *Messages* say that it is not able to find the styles dir, it really means that it is not able to find the styles files. > Checked that it comes back it I use emacs23; goes away if I use > emacs24 Checked that the messages when it works in emacs24 are like > thus: ODT exporter (and hence the style files) made it's appearance in Emacs24. (i.e., There is ALWAYS a styles file that the exporter can safely fallback to.) The styles file that the ODT exporter ACTUALLY USES may come from stock Emacs and which may trail behind the git repo over a period of time. There is no ODT exporter in stock Emacs23. So fallback MAY fail. Stock Emacs has styles file under: C-h v data-directory If you installed Org as a standalone package, use apt to find out where it is located. Someone reported a bug on ox-odt.el paths not being modified when the ODT exporter moved from contrib/ to lisp/ directory in git repo. (Interested people can investigate and propose a patch.) I don't have a link to that post right now. The way make system treats `org-odt-data-dir' is a bit flaky. I didn't pursue the issue further because I felt it is pointless arguing with some people.
Re: [O] No ODT export option
Debian lags quite a bit (from few months to years). It is difficult to say what version they are packaging. The best and easiest way to install latest Org would be to via GNU ELPA or Org ELPA. See http://orgmode.org/elpa.html. M-x list-packages Once you insall the package, restart Emacs and do M-x customize-variable org-export-backends and enable ODT. ps: If you are new to Emacs/Org, you will have less troubles if you start with an empty .emacs (or more specifically a .emacs that doesn't have any Org specific configuration.) Hendrik Boom writes: > On Fri, 10 Jan 2014 11:32:55 -0500, Ista Zahn wrote: > >> Hi Ken, >> >> ODT export isn't enabled by default. You can enable it by putting >> >> (require 'ox-odt) >> >> in your config file and restart emacs. >> >> Best, >> Ista > > I'm having this problem on Debian testing, but not on Debian stable. > I have installed the org-mode package on both systems. > > Inserting (require 'ox-odt) at the end of my !/.emacs file gives me > Warning (initialization): An error occurred while loading `/home/ > hendrik/.emacs': > > File error: Cannot open load file, ox-odt > > To ensure normal operation, you should investigate and remove the > cause of the error in your initialization file. Start Emacs with > the `--debug-init' option to view a complete error backtrace. > > so it doesn't look as if it worked. > > For the record, there is a /usr/share/emacs/site-lisp/org-mode/ ox-odt.el > file. > > Also, export to html works, presumably using the ox-html.el file in that > same directory, and I don't have to say (require 'ox-odt). I'd preume > that file is found by the same mechanism, so not finding ox-odt by > default is a bit of a puzzle. > > The Debian testing system, which works, has similar files in teh same > place, but their names start with org- instead of ox-
Re: [O] Org Export to ODT Problem Files
Aric Gregson writes: >>> 4. Figure and table references are by section, sort of like old >>> fashioned latex. > > For me, I am not writing a book or anything very long, just > manuscripts. Thus, I would prefer just to label each figure in order and > each table in order. I would therefore get Figure 1, Figure 2, etc and > Table 1, Table 2, etc in the order of appearance in the text. There is > no reference to section that way. You are looking for this (custom-set-variables '(org-odt-display-outline-level 0))
Re: [O] Citations and references in ODT
Aric Gregson writes: > OpenDocument export failed: Symbol's function definition is void: > org-element-cache-reset You have some installation issues. Try the following commands and try to address any inconsistencies in the various paths. C-h v org-version M-x find-library org-loaddefs M-x find-library ox M-x find-library ox-odt M-x find-library ox-jabref M-x list-load-path-shadows org
Re: [O] Citations and references in ODT
Aric Gregson writes:
> Ken Mankoff writes:
>
>> I find the ODT export very useful. Working on another document imported
>> from LaTeX I have a lot of \citep{} and \citet{} in addition to \cite{}. Is
>> it possible for ox-jabref.el to support this even if it does not
>> distinguish between the T and P?
>
> On a similar note, would it be possible to add support for the markdown
> style of references?
>
> [@Authoryear; @anotherauthoryear]
>
> I have so many like this across files.
This will be an one-off change, so I am hesitant to consider this.
Side Note:
==
As far as Org is concerned, Citations are not standardized (i.e., They
are not defined as part of org-syntax [1]). But, the current practive
is to support \cite[]{ } style of markups using non-core, contrib
modules like ox-bibtex and ox-jabref.
I am interested in considering all suggestions or use-cases that extends
or improves upon the current practice. For example, handling of prenote
and postnote arguments[2, 3].
[1] http://orgmode.org/worg/dev/org-syntax.html
[2] http://permalink.gmane.org/gmane.emacs.orgmode/80846
[3] This would require changes to JabRef *.layout files.
> Thanks, Aric
Re: [O] Citations and references in ODT
I have introduced a new variable `org-odt-cite-regexp'. You can use M-x
customize-variable to change the default settings. [1, 4]
I would like to (eventually) add support for prenote and postnote
options for ODT export [2]. These intext options could be quite useful
when citation references use text rather than numbers [3].
[1] Download ox-odt.el and ox-jabref.el from my private repo at
http://repo.or.cz/w/org-mode/org-kjn.git
[2] http://orgmode.org/worg/org-tutorials/org-latex-export.html
[3]
(custom-set-variables
'(org-jabref-odt-citation-transcoders
(quote (org-jabref-odt-citation-reference/text
. org-jabref-odt-bibliography/numbered
[4]
,[ C-h v org-odt-cite-regexp RET ]
| org-odt-cite-regexp is a variable defined in `ox-odt.el'.
| Its value is
|
"\\(?:\\(cite[[:word:]]*\\)\\(\\(?:\\[\\(?:.\\|\n\\)*]\\)?\\)\\({.*?}\\)\\)"
|
| Documentation:
| Regular expression to identify \cite[]{} fragments.
| After a match against this regular expression, various portions
| of the latex fragment - command, options and argument - is
| available in `match-string's 1, 2 and 3 respectively.
|
| For example, given the following cite command
|
| \citep[see][chap. 2]{jon90}
|
| a match against the above regexp, will result in `match-string's
| as below:
|
| 1 => citep
| 2 => [see][chap. 2]
| 3 => {jon90}.
|
| You can customize this variable.
|
| This variable was introduced, or its default value was changed, in
| version 24.4 of Emacs.
|
| [back]
`
Ken Mankoff writes:
> Hi,
>
> I find the ODT export very useful. Working on another document
> imported from LaTeX I have a lot of \citep{} and \citet{} in addition
> to \cite{}. Is it possible for ox-jabref.el to support this even if it
> does not distinguish between the T and P?
>
> I edited the line near the bottom with the regex and changed
>
> (value (∧ (string-match "cite{\\(.*?\\)}" latex-frag)
>
> to
>
> (value (∧ (string-match "cite?{\\(.*?\\)}" latex-frag)
>
> But it did not help.
>
> -k.
Re: [O] Citations and references in ODT
Ken Mankoff writes: > I'm now trying to get ODT w/ references and failing. Show me a snippet that causes the problem. You can COMMENT a tree or add a :no-export tag to bisect. Or you copy can copy over a subtree and experiment with it. > The message I get is: > > OpenDocument export failed: Format specifier doesn't match argument > type Difficult to say where it is coming from. > I did the following based on your instructions and some guessing. > > 1) I put ox-odt.el and ox-jabref.el and etc/schema and etc/styles in > my ~/emacs.d/elpa/org-2014017 folder. Some of that involved > overwriting existing files. At the minimum you may have to M-x byte-compile-file ox-odt.el and may be fix regenerate autoloads. See the recipe at the end of this message for a cumbersome but a fool proof method. > 2) I downloaded JabRef application (I'm on OS X), and copied the JAR > file from inside it into your unit test folder. I ran "java -jar > jabref" and opened MyLibrary.bib with the program and saved it. I did > this because I assume I have to tell JabRef about the bib file? You need to install the Chicago jar file which contain the *.layout file that JabRef needs. >From the command line look at the output formats that JabRef reports. You should see ODF there. Do M-x find-library ox-jabref.el and follow the instructions there. ODT exporter has it's own citaion mechanism and doesn't depend on ox-bibtex.el. > If I export to HTML, I do see all the equations, despite the MathToWeb > error. HTML uses MathJax while ODT uses MathToWeb. Two different things. Look at M-x org-export-as-odf-TAB for checking against simple latex equations. Check if the latex equations are png files or something else. > If I export to ODT, emacs reports > > OpenDocument export failed: Format specifier doesn't match argument > type > > I notice at the top of your test-new.org file the following line: > > #+ODT_STYLES_FILE: "~/list-table-1.odt" You can extract the relevant sections from test-new.org and experiment with the excerpts. > But I cannot find a list-table-1.odt anywhere in the unit test ZIP > file or in your org-mode git repo (which I cloned, but elsewhere and > then copied the files from there to my org-mode elpa repo). One thing you could do is this 1. Download org-*.tar file with wget or firefox. 2. Untar it. 3. Replace ox-odt.el, the style files and copy over the ox-jabref.el file. 4. Re-create the tar file (with the new files). 5. Do M-x package-install-file to install the new elpa. > Any hints about where I took a wrong step will be appreciated. > > Thanks, > > -k.
Re: [O] Org Export to ODT Problem Files
> I'm slow at learning the machinery behind Open Document Format Oh, OK. If you say so.
Re: [O] Citations and references in ODT
Aric writes: Ken Mankoff gmail.com> writes: ox-odt.el supports citation via ox-jabref.el. Use my private files for JabRef support === JabRef support is NOT part of Org distribution. It is part of my private repo at: http://repo.or.cz/w/org-mode/org-kjn.git I have shared instructions on how to use my git repo at http://lists.gnu.org/archive/html/emacs-orgmode/2013-12/msg00522.html Don't "git pull" my repository (I keep rebasing it against Org master repo). Just copy relvant files. Unit Test file for citations (with a sample .bib file) == The following link http://lists.gnu.org/archive/html/bug-gnu-emacs/2013-09/msg00572.html has link a test-odt.zip file which has jar file, a .org file and a .bib file. If you run in to issues, write me a note and I will happy to make fixes or enhancements. If you find ox-jabref.el support useful and you want ox-odt.el supported by the original author (that would be me) you can leave a note (or petition emacs-devel) for ...
Re: [O] Citations and references in ODT
Aric writes: Ken Mankoff gmail.com> writes: ox-odt.el supports citation via ox-jabref.el. Use my private files for JabRef support === JabRef support is NOT part of Org distribution. It is part of my private repo at: http://repo.or.cz/w/org-mode/org-kjn.git I have shared instructions on how to use my git repo at http://lists.gnu.org/archive/html/emacs-orgmode/2013-12/msg00522.html Don't "git pull" my repository (I keep rebasing it against Org master repo). Just copy relvant files. Unit Test file for citations (with a sample .bib file) == The following link http://lists.gnu.org/archive/html/bug-gnu-emacs/2013-09/msg00572.html has link a test-odt.zip file which has jar file, a .org file and a .bib file. If you run in to issues, write me a note and I will happy to make fixes or enhancements. If you find ox-jabref.el support useful you can leave a note to or petition Stefan Monnnier (and particularly Michale Albinus, Juanama and Jay Belanger).
Re: [O] Org Export to ODT Problem Files
Bastien writes: > Please try with Org 8.2.5 or later, an issue with multiple figures > not showing up in LibreOffice 4.1.x has been fixed. Cool. While you are at it, you can take care of export issues with non-utf-8 (spanish encoded) Org files as well. http://lists.gnu.org/archive/html/emacs-orgmode/2013-10/msg00873.html Jambunathan K. Git Repo: http://repo.or.cz/w/org-mode/org-kjn.git
Re: [O] Org Export to ODT Problem Files
Comparison is nice. Using pandoc to do org->odt is definitely substandard. Aric writes: > Thank you very much for the upgrade notice. The export to ODT from org-mode > works very well now. There are pluses and minuses it seems between pandoc and > org export. > > Org export -> > 1. Includes figures and tables > 2. Includes pretty code mark-up You can suppress fontification with this variable. C-h v org-odt-fontify-srcblocks > 3. Lacks latex code export Use dvipng or mathtoweb. 1. Dvipng Pro: Less problematic Con: Uses png images of the formulae. 2. MathToWeb Pro: Uses MathML Con: MathToWeb is new kid on the block. May prove to be problematic with more complex formulae. If ltx->mathml conversion is problematic for some equations, you can create "ODF files" (OpenDocumentFormula files created with LibreOffice Math) by hand and insert an Org link to them. > 4. Figure and table references are by section, sort of like old > fashioned latex. But tell me what you yourself want here. I have some ideas on how xrefs can be improved for the section titles. See http://lists.gnu.org/archive/html/emacs-orgmode/2013-12/msg00585.html I would like to hear what things you desire for xrefs to tables, figures and equations. You were making some remarks about position of captions...
Re: [O] Colorizing 'emacs-lisp' when it is exported?
Sharon Kimble writes: > Re: Colorizing 'emacs-lisp' when it is exported? Search for htmlize or htmlfontify in the Org-mode and Emacs manuals. > For once, google has drawn a blank, unfortunately! Emacs is self-documenting. If you are serious about using Emacs you will ditch google (and even Emacswiki).
Re: [O] tricky odt export needs
I will respond to other items as I visit them. Meanwhile, I would like to add the following note for discussion. Christian Moe writes: > When headings are not numbered in export (#+options: num:nil), current > ODT export outputs a cross-reference with a descriptive text equal to > the heading text of the item the dedicated target is in. When we are typesetting a xref in a backend - I can authoritatively speak for the ODT backend - we need not be resticted to "ONE-OF" but can have "ANY-COMBINATION-OF" descriptors. What I mean is this: In the pdf version of Emacs info manuals one typically sees all three of a Section number AND a Description AND a Page number, something like: See Section 3.1 [Tropical Storms], page 24. In Org context, I am wondering whether there is such a need. http://www.gnu.org/software/texinfo/manual/texinfo/html_node/Reference-Syntax.html#Reference-Syntax (There are some variations on the xref markup to restrict whether te "See" is present or not, capitalized or not) http://www.gnu.org/software/texinfo/manual/texinfo/html_node/Cross-Reference-Commands.html#Cross-Reference-Commands
Re: [O] Warning (initialization): Your `load-path' seems to contain your `.emacs.d' directory
Paul Harper writes: > "Warning (initialization): Your `load-path' seems to contain > your `.emacs.d' directory: /home/username/.emacs.d/ > This is likely to cause problems... > Consider using a subdirectory instead, e.g.: > /home/username/.emacs.d/lisp" (I know nothing about starter kit) On a related note, this warning occurs with Emacs from bzr trunk. The problem surfaced in the help list. See http://permalink.gmane.org/gmane.emacs.help/94823
Re: [O] tricky odt export needs
Christian Moe writes: > You can do cross-references with ordinary links. Have a look at the > manual section 4.2, "Internal links". However, what you get out of the > box is textual references to e.g. section headings, not page > references. You can change that for each reference individually by > right-clicking on them in LibreOffice. There should be a way to get > page references by default, but off the cuff, I'm not sure how. I am interested in rolling out support for xref by pagenumbers. I would like to know what the standard or recommended practice is like. So, when one says "I want pagenumbers for xref", what xref-es they have in mind. Do they mean ONE-or-SOME-or-ALL of a xref to outline headings, figure, table, source listings, formula etc. Personally I wouldn't recommend use of filters to end users. Filters are useful for programmers not for the layman.
Re: [O] Bug: Bad ODT files when including multiple images [7.9.3f (release_7.9.3f-17-g7524ef /usr/share/emacs/24.3/lisp/org/)]
The fix is available in private repository: http://repo.or.cz/w/org-mode/org-kjn.git As far as schema validation with .rnc files go, draw:name is an optional attribute of draw:frame. So, I am not sure why LibreOffice is insisting on draw:name to exist and be unique. Due to the above issue, I have also retired the support for short-caption. See my not pertaining to LibreOffice upgrades here: http://lists.gnu.org/archive/html/emacs-orgmode/2013-12/msg00477.html Due to this issue, I proposed that I maintain ox-odt.el right within Emacs bzr repo. Unfortunately, it resulted in some heated exchanges. http://lists.gnu.org/archive/html/emacs-devel/2013-12/msg00509.html To the people who rely on ODT exporter for their day to day use and want it as part of Emacs 1. Find someone with Copyright Assignment to fix the critical issue(s). 2. Write to Gnu/Linux distributors - Debian, Gentoo etc - and persuade them to apply patches from my private repo before building the org-mode or Emacs deb packages. Download the files. Don't use git. The files relevant to ODT are 1. lisp/ox-odt.el 2. etc/styles 3. etc/schema 4. contrib/lisp/ox-jabref.el (3) above is optional. (4) is needed if you need export citations with JabRef. Tim writes: >> Let me upgrade my LibreOffice and report back. > Jambunathan, >was wondering if you had a chance to look at this error ? I can confirm > it is an issue on my Ubuntu 13.10 system with : >- emacs 24.3.1 >- org-mode 8.2.4 (org-plus-contrib elpa package 20131216) >- libreoffice 4.1.3.2 > > I use the odt export to create student handouts and *really* don't want to go > back through 200+ documents to add captions to all of the images ! > > Thanks > > -Tim
Re: [O] Bug: Bad ODT files when including multiple images [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)]
Tim writes: > Jambunathan, >was wondering if you had a chance to look at this error ? I can confirm > it is an issue on my Ubuntu 13.10 system with : >- emacs 24.3.1 >- org-mode 8.2.4 (org-plus-contrib elpa package 20131216) >- libreoffice 4.1.3.2 I can see the problem on my side. > I use the odt export to create student handouts and *really* don't > want to go back through 200+ documents to add captions to all of the > images ! This issue is a bit unfortunate. Please don't modify your Org files. I will circulate a fix - if not a fix, atleast a workaround - in another day. Jambunathan K.
Re: [O] new odt-exporter: problems with formatting in captions
Wrt items (1) and (2), I am planning to remove the support for short
captions. (The caption going as part of table:name or draw:name) as
part of fix for
http://lists.gnu.org/archive/html/emacs-orgmode/2013-12/msg00100.html
The fix is not ready yet. I am just feeling lazy after having not
looked at the code for almost an year now.
NOTE: If someone knows how to accommodate short captions (so that an
that an Index/TOC could be generated from within LibreOffice based on
it, please let me know.)
For the benefit of audience, if you use embedded images in your document
the document produced by the ODT exporter will be openable by
LibreOffice < 4.0 but not with LibreOffice > 4.1. (In other words,
LibreOffice folks have introduced some backward incompatible changes.)
To ensure that the document produced by the exporter is usable resave
the document from within LibreOffice. (i.e., make some trivial changes
to the ODT document and do a save again). This way the XML produced by
the exporter will be re-written by LibreOffice and the problem will be
averted.
As a side note, I am discussing with Emacs maintainers whether they
would be comfortable about having me maintain the exporter right from
within Emacs repo. I am not sure how the discussion will go.
http://lists.gnu.org/archive/html/emacs-devel/2013-12/msg00509.html
martin.guert...@gmx.de (Martin Gürtler) writes:
> Hi,
>
> I just converted a 150 page document I used to convert to odt with the old
> exporter. Following problems occurred:
>
> 1. table with #+CAPTION
>If the caption contains formatting (~, ==, _, ^), the exporter
>produces an invalid content.xml.
>
>minimal example:
>
> ---8<
> #+OPTIONS: num:t toc:nil \n:nil @:t ::t |:t ^:{} -:t f:t *:t <:nil
>
> * First paragraph
> #+CAPTION: A_{1}^{2}
> | head 1| head2|
> |---+--|
> | content 1 | content2 |
> ---8<
>
> The problem can be seen in the following xml fragment:
>
> ---8<
> table:name="A text:style-name="OrgSubscript">1 text:style-name="OrgSuperscript">2 ">
> ---8<
>
> The table:name attribute ends prematurely at the "OrgSubscript". This
> could probably be mended by using single quotes for these attributes
> inside attributes.
>
> 2. again #+CAPTION
>
>if the caption contains a string with /escaped/ underlines (please
>note the #+OPTION ^:t)
>
> ---8<
> #+OPTIONS: num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:nil
>
> * First paragraph
> #+CAPTION: MMDD\_hhmmss.csv.
> | head 1| head2|
> |---+--|
> | content 1 | content2 |
> ---8<
>
> The escaped _ is not detected; instead, a literal \ and subscript
> are detected, and teh document is invalid as above. This escaping
> seems not to be mentioned in the documentation, probably because it
> is no longer valid. Might be of interest to people who want to
> convert old documents.
>
> 3. the \ref syntax seems not to work anymore; substituting by \ref{text}
>by [[text]] worked.
>
> 4. Empty lines between #+NAME and the respective table are no longer tolerated
>
> remarks: I like the new smart quotes. More comfortable than putting in
> the utf characters via C-8-RET (which is handy, though, for simple
> formulae).
>
> Regards
>
> Martin
Re: [O] Set org-file-apps to open a *.doc file under linux with Word ?
Nick Dokos writes:
> Off the top of my head, I would say
>
> (add-to-list 'org-file-apps
> '("\\.doc" . "env WINEPREFIX=\"/home/AW/.wine-office\" wine
> \"C:\\windows\\command\\start.exe\" /Unix
> \"/home/AW/.wine-office/dosdevices/c:/users/AW/Start Menu/Programs/Microsoft
> Office/Microsoft Word 2010.lnk\""))
>
>
> i.e. just the command you provided enclosed in double quotes, except that
> certain characters within have to be escaped:
The easiest way to get the same effect is to use
M-x customize-variable RET org-file-apps RET
and specify a command. Once it is saved, the .emacs will have the
resulting "nightmarish string" :-)
Another way to "quote" a string would be to use
M-x pp-eval-expression RET (read-string "Enter string: ") RET
and copy-paste the output from *Pp Eval Output* to .emacs or .el file.
Re: [O] Set org-file-apps to open a *.doc file under linux with Word ?
AW writes: > I found out, that things are much more complicated: Did you try my suggestion? What happened? I gave a snippet.el. You just need to copy paste that to .emacs. It is easy to figure out where and how. (I know nothing about shell programming or environment variables and such things) > Thanks to you and everyone who offered help, but it was not a good > idea. You are running away. We aren't. Give it a try, Buddy. We will figure out something and make you happy.
[O] FYI Emacs-24.4 survey
http://www.emacswiki.org/emacs/FrequentlyEnabledPackages_Emacs244_Survey
Re: [O] Set org-file-apps to open a *.doc file under linux with Word ?
AW writes: > Thank you, customization worked, but it did not start word -- I'm going > another way now. I am playing a guessing game and really don't know what I am saying. Try this. M-: (shell-quote-argument (read-string "Enter string:")) When prompted enter whatever wine whatever "%s" Now put whatever string you get in *Pp Eval Output* DIRECTLY in to your .emacs. See the attached snippet.el for what I get. Instead of passing env as part of the command, I think you can add this to your .emacs. (setenv "WINEPREFIX" "/home/AW/.wine-office") You can also do M-x setenv to set environment variables. snippet.el Description: application/emacs-lisp
Re: [O] Set org-file-apps to open a *.doc file under linux with Word ?
AW writes: > Thank you, customization worked, but it did not start word -- I'm going > another way now. I am playing a guessing game and don't know what I am saying. Try this. M-: (shell-quote-argument (read-string "Enter string:")) When prompted enter "%s" Now put whatever string you get in *Pp Eval Output* DIRECTLY in to your .emacs. See the attached snippet.el for an idea of what I get. Instead of passing env as part of the command, I think you can add this to your .emacs. (setenv "WINEPREFIX" "/home/AW/.wine-office") You can also do M-x setenv to set environment variables. snippet.el Description: application/emacs-lisp
Re: [O] Set org-file-apps to open a *.doc file under linux with Word ?
Nick Dokos writes:
> Off the top of my head, I would say
>
> (add-to-list 'org-file-apps
> '("\\.doc" . "env WINEPREFIX=\"/home/AW/.wine-office\" wine
> \"C:\\windows\\command\\start.exe\" /Unix
> \"/home/AW/.wine-office/dosdevices/c:/users/AW/Start Menu/Programs/Microsoft
> Office/Microsoft Word 2010.lnk\""))
>
>
> i.e. just the command you provided enclosed in double quotes, except that
> certain characters within have to be escaped:
>
> " -> \"
> \ -> \\
>
> The long string will probably be broken up into multiple lines by some
> mailer but it is supposed to be one long string with no newlines. I
> don't know if the spaces in the path will cause problems.
>
> Untested (except that I did evaluate the add-to-list and got no errors):
> no Word and no wine here.
>
> BTW, why not LibreOffice? Does it mishandle your .doc files?
>
> Nick
The easiest way to get the same effect is to use
M-x customize-variable RET org-file-apps RET
and specify a command. Once it is saved, the .emacs will have the
resulting "nightmarish string" :-)
Another way to "quote" a string would be to use
M-x pp-eval-expression RET (read-string "Enter string: ") RET
and copy-paste the output from *Pp Eval Output* to .emacs or .el file.
Re: [O] Bug: Bad ODT files when including multiple images [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)]
Christian Moe writes: > This problem was also reported by Tyler Smith a couple of weeks back. I was able to open test.odt provided by Tyler just fine. Hence I did not follow up the post (IIRC, Christian was also indicating a "no issue".) http://permalink.gmane.org/gmane.emacs.orgmode/78579 I am using LibreOffice 4.0.1.2. Tyler says he is using 4.0.4.2. OP is using LibreOffice-4.1.3.2. Is it a problem only with recent LibreOffices? Let me upgrade my LibreOffice and report back.
Re: [O] Handshake: Org-mode + Emacs releases
Nicolas Goaziou writes: > Hello, > > Jambunathan K writes: > >> I am a bit apprehensive that (what you think as) essentials MAY get >> missed in Vanilla Emacs proper. So it would be good if you could >> communicate with Emacs developers the Org-mode features that you want >> packed in the upcoming Emacs release. (If this is already communicated, >> well and good) > > I am no maintainer so I cannot tell which Org revision should be merged > with Emacs. Just to clarify, I was interested in your comments as a developer who is in-charge of org-element and ox & Co. Essentially, I was asking a convoluted question about the roadmap for features that you have taken responsibility for vis-a-vis current Emacs release. > (modulo some features that might be cherry picked from master) and > would be the obvious safe choice for a quiet end of year. Ok. I am sure you will work this out with whoever is merging... > FWIW, considering the 15 days time frame we have, I think 8.2.3 family > is stable enough > 8.3 release (i.e. built from master) has some interesting features, but > may require more work from Org developers during pretest phase. I take your answer to mean that you don't foresee anything substantial to be added to the current feature set. It's possible for you to buy time if you would like to see more feature-lets added or stabilized.
[O] Handshake: Org-mode + Emacs releases
Nicolas Nicolas Goaziou writes: > I have a half baked patch which allows to use export framework to handle > radio tables. I'll try to complete it by the end of the year and propose > it on the ML. I see that you are adding features and doing a very quick iteration. Nothing wrong with it and each sprint has been well-timed and planned. I am a bit apprehensive that (what you think as) essentials MAY get missed in Vanilla Emacs proper. So it would be good if you could communicate with Emacs developers the Org-mode features that you want packed in the upcoming Emacs release. (If this is already communicated, well and good) Stefan was indicating mid-December for the current release. Needless to say, having features bundled as part of pre-test builds would get more beta-testing and coverage.
