[O] org-capture: keeping window visible during date entry
Hello, I recently switched from remember to org's new capture facility which seems to work fine. However, an issue I already had with remember is still bothering me, perhaps someone knows a good solution: I often call org-capture from within a buffer containing some relevant context, for example an e-mail message displayed by gnus. The emacs window created by org-capture that allows to choose a template is created below the two Gnus windows showing the group and the message. My org-capture templates require entering a date. During the subsequent date entry, the gnus windows are not visible anymore (I only see the nascent buffer with the entry to be captured and a window showing the emacs calendar). This is impractical, because the e-mail message often contains the very date I would like to enter. How to ensure that the buffer which was active when org-capture was executed remains visible during date entry? Thanks, Christoph
Re: [O] Checkboxes for description lists
Hello Nicolas,
Nicolas Goaziou wrote:
Sebastien Vauban
wxhgmqzgw...@spammotel.com writes:
It seems we can't put footnotes in the left part of the
description. Is it intended? Could that restriction be removed?
That's not really intended, and the fix is easy, but I have a question
first: how would it be rendered in LaTeX?
Apparently,
\item[tag text\footnote{contents}] item's contents
isn't valid.
I would then say just after the [...] part, so that it stays closer to where
we want to put it.
But, then, you'll say the user can already do that. True.
Best regards,
Seb
--
Sebastien Vauban
Re: [O] org-e-html: Including ATTR_HTML: title=hover text
Hello, William Crandall bc3141...@gmail.com writes: I confess I am puzzled by the choice to drop the ability to apply attributes to links. That's not a choice /per se/, merely an annoying side-effect of moving to an overall better paradigm. Org input: -- A paragraph with three papers, and an image: #+ATTR_HTML: title=Paper #1 [[./local/01.html][a first paper]] followed by #+ATTR_HTML: title=Paper #2 [[./local/02.html][a second paper]] which describe stuff. It then offers a cat #+ATTR_HTML: title=Some cats alt=Cat image [[./local/cats.png]] and finally a third, PDF paper #+ATTR_HTML: title=Paper #3 [[./local/03.pdf][a third paper]] -- Old exporter: -- p A paragraph with three papers, and an image: a href=./local/01.html title=Paper #1a first paper/a followed by a href=./local/02.html title=Paper #2a second paper/a which describe stuff. It then offers a cat img src=./local/cats.png title=Some cats alt=Cat image / and finally a third, PDF paper a href=./local/03.pdf title=Paper #3a third paper/a /p -- I believe that this ability, this specificity within paragraphs, is generally quite useful, and I hope that you will consider it for the new exporter. I understand your problem, but inserting ATTR_HTML keywords in a paragraph isn't possible anymore. I cannot allow that as it would defeat a fundamental change in the new Org syntax. Though, I'm open to any other suggestion. For example, link's syntax could be extended to allow attributes, much like Babel's inline source blocks or calls. It would probably require many changes to core, though. ATTR_HTML could also accept a list of properties that would be applied in order to each link in the paragraph. But it wouldn't scale well with a large number of links. I'm certain there are better solutions out there. Regards, -- Nicolas Goaziou
Re: [O] new (LaTeX) exporter and date formatting
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Side note:
Ideally, in my opinion, the LaTeX-exporter would honor the
#+LANGUAGE: XX
setting and change the babel-settings accordingly
That seems reasonable. Is there any translation table between language
symbols and Babel options?
Not that I am aware of. But we could start one quite easily. I got
this list of LaTeX-babel supported languages from
http://www.tug.org/texlive/Contents/live/texmf-dist/doc/generic/babel/babel.pdf:
(just a quick hack...)
The following patch should add the language option according to LANGUAGE
keywords if babel package is explicitly loaded in preamble.
Is it what you had in mind? I'm a bit reluctant to load babel package if
not present.
Regards,
--
Nicolas Goaziou
From 1f9a6385e961e61d8b5e5e4d56889c7b2bd9f82b Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou n.goaz...@gmail.com
Date: Thu, 14 Jun 2012 12:57:35 +0200
Subject: [PATCH] org-e-latex: Set Babel language according to LANGUAGE
keyword
* contrib/lisp/org-e-latex.el (org-e-latex-babel-language-alist): New
variable.
(org-e-latex--guess-babel-language): New function.
(org-e-latex-template): Set babel language according to LANGUAGE keyword.
---
contrib/lisp/org-e-latex.el | 93 ++-
1 file changed, 83 insertions(+), 10 deletions(-)
diff --git a/contrib/lisp/org-e-latex.el b/contrib/lisp/org-e-latex.el
index 287556f..6feb8cf 100644
--- a/contrib/lisp/org-e-latex.el
+++ b/contrib/lisp/org-e-latex.el
@@ -147,6 +147,63 @@ structure of the values.)
+;;; Internal Variables
+
+(defconst org-e-latex-babel-language-alist
+ '((af . afrikaans)
+(bg . bulgarian)
+(bt-br . brazilian)
+(ca . catalan)
+(cs . czech)
+(cy . welsh)
+(da . danish)
+(de . german)
+(de . germanb)
+(de-at . austrian)
+(de-at . naustrian)
+(de-de . ngerman)
+(el . greek)
+(en . english)
+(en-au . australian)
+(en-ca . canadian)
+(en-gb . british)
+(en-ie . irish)
+(en-nz . newzealand)
+(en-us . american)
+(es . spanish)
+(et . estonian)
+(eu . basque)
+(fi . finnish)
+(fr . frenchb)
+(fr-ca . canadien)
+(gl . galician)
+(hr . croatian)
+(hu . hungarian)
+(id . indonesian)
+(is . icelandic)
+(it . italian)
+(la . latin)
+(ms . malay)
+(nl . dutch)
+(no-no . nynorsk)
+(pl . polish)
+(pt . portuguese)
+(ro . romanian)
+(ru . russian)
+(sa . sanskrit)
+(sb . uppersorbian)
+(sk . slovak)
+(sl . slovene)
+(sq . albanian)
+(sr . serbian)
+(sv . swedish)
+(ta . tamil)
+(tr . turkish)
+(uk . ukrainian))
+ Alist between language code and corresponding Babel option.)
+
+
+
;;; User Configurable Variables
(defgroup org-export-e-latex nil
@@ -815,12 +872,26 @@ For non-floats, see `org-e-latex--wrap-label'.
label-str
(org-export-data (car caption) info))
+(defun org-e-latex--guess-babel-language (header info)
+ Set Babel's language according to LANGUAGE keyword.
+HEADER is the LaTeX header string. INFO is the plist used as
+a communication channel. Return the new header.
+ (let ((language-code (plist-get info :language)))
+;; If no language is set, return HEADER as-is.
+(if (not (stringp language-code)) header
+ (if (not (string-match usepackage\\[\\(.*\\)\\]{babel} header))
+ header
+ (let ((options (save-match-data
+ (org-split-string (match-string 1 header) ,)))
+ (language (cdr (assoc language-code
+org-e-latex-babel-language-alist
+ (if (member language options) header
+ (replace-match (mapconcat 'identity (cons language options) ,)
+ nil nil header 1)))
+
(defun org-e-latex--guess-inputenc (header)
Set the coding system in inputenc to what the buffer is.
-
-HEADER is the LaTeX header string.
-
-Return the new header.
+HEADER is the LaTeX header string. Return the new header.
(let* ((cs (or (ignore-errors
(latexenc-coding-system-to-inputenc
buffer-file-coding-system))
@@ -936,12 +1007,14 @@ holding export options.
^[ \t]*documentclass\\(\\[.*?\\]\\)
class-options header t nil 1)
header
- (org-e-latex--guess-inputenc
- (org-splice-latex-header
- document-class-string
- org-export-latex-default-packages-alist ; defined in org.el
- org-export-latex-packages-alist nil ; defined in org.el
- (plist-get info :latex-header-extra))
+ (org-e-latex--guess-babel-language
+ (org-e-latex--guess-inputenc
+ (org-splice-latex-header
+ document-class-string
+ org-export-latex-default-packages-alist ; defined in org.el
+ org-export-latex-packages-alist nil ; defined in org.el
+ (plist-get info :latex-header-extra)))
+ info
;; 3. Define alert if not yet defined.
\\providecommand{\\alert}[1]{\\textbf{#1}}\n
;; 4. Possibly limit depth for headline numbering.
--
Re: [O] Bug: Line breaks in exported LaTeX code [7.8.11]
Hi Eric
Thanks! No, I hadn't thought of that, silly me.
It turns out that the following line in my .emacs caused the problems:
(add-hook 'LaTeX-mode-hook 'longlines-mode)
So now I have commented that one out and the export works fine and has
all the line breaks I had expected. I guess I will just enable longlines
mode manually when editing LaTeX from now on.
Thanks again for the pointer!
Cheers
Uffe
On 06/13/2012 04:57 PM, Eric S Fraga wrote:
Uffe Høgsbro Thygesenu...@aqua.dtu.dk writes:
Greetings Orgs
When exporting an .org file to LaTeX, no line breaks are inserted into
the LaTeX source code. With default options from a fresh install, the
LaTeX code will not compile, because documentclass information appears
on the first line of the LaTeX source, which is a comment:
% Created 2012-06-08 Fri 12:58 \documentclass{article} [...]
This doesn't happen to me. Have you tried with emacs -Q to ensure
that it's not something in your configuration?
Re: [O] Using Org for a dissertation
Eric Schulte eric.schu...@gmx.com writes: 1) Section labels and other in-document references. It's nice that Org generates these on export, but I need to be able to assign and use labels that will not change if the document is reordered. I know I can simply add such labels via a \label command, but I am worried that using them in addition to Org's autogenerated labels might cause numbering problems in LaTeX. I've not run into any such problems. I tend to construct all of my labels through Org-mode (which works well for export to both HTML and LaTeX). Could you describe how to do section links and references from within Org. I have tried to figure this out for a while now. The only solution I can find (on Worg) depends on precise section names, which is not so stable. I use the new latex export engine [2] http://gitweb.adaptive.cs.unm.edu/dissertation.git/tree This link is unfortunately dead. –Rasmus -- Send from my Emacs
Re: [O] org-program-exists vs executable-find
Da: Sebastien Vauban wxhgmqzgw...@spammotel.com Inviato: Venerdì 20 Aprile 2012 22:24 Bastien wrote: If there is an equivalent of `which' on windows let me know, Not that I know the command where [1][2] cheers, Giovanni [1] http://stackoverflow.com/questions/304319/is-there-an-equivalent-of-which-on-windows [2] http://superuser.com/questions/207707/what-is-windows-equivalent-of-which-command-in-linux-is-there-is-equivalent Some versions of Windows (I think Windows 2003 and up) have the where command: c:\where ping C:\Windows\System32\PING.EXE
Re: [O] [latex] Problems with old exporter (for Beamer) and with new exporter
Hello Nicolas,
Nicolas Goaziou wrote:
Sebastien Vauban writes:
With the new exporter, most things work. What does not work:
- macro does not get executed (no string in orange color),
Macro are meant to produce contents, not to talk to back-ends. Every text
they produce will be protected.
Do you mean the template must be pure text?
Do you mean that a thing such as
http://frozenlock.org/2011/11/05/on-the-fly-key-sequence-insertion/ won't work
anymore?
- the =\end{verbatim}= disappears from the LaTeX output
This is a limitation from LaTeX: you cannot have \end{verbatim} string
within a verbatim environment.
OK, I thought it would be in a listings. But I did not customize the variable
`org-e-latex-listings' (well the old exporter one).
Though, now, when trying to export to LaTeX (with the new exporter and
up-to-date Org[1]), I get an error:
--8---cut here---start-8---
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-match(^[ ]*\\[\\(NO-\\)?DEFAULT-PACKAGES\\][ ]*\n? nil)
(if (string-match ^[ ]*\\[\\(NO-\\)?DEFAULT-PACKAGES\\][ ]*\n?
tpl) (setq rpl (if (or (match-end 1) (not def-pkg))
(org-latex-packages-to-string def-pkg snippets-p t)) tpl (replace-match rpl t t
tpl)) (if def-pkg (setq end (org-latex-packages-to-string def-pkg snippets-p
(let (rpl (end )) (if (string-match ^[
]*\\[\\(NO-\\)?DEFAULT-PACKAGES\\][ ]*\n? tpl) (setq rpl (if (or
(match-end 1) (not def-pkg)) (org-latex-packages-to-string def-pkg
snippets-p t)) tpl (replace-match rpl t t tpl)) (if def-pkg (setq end
(org-latex-packages-to-string def-pkg snippets-p (if (string-match
\\[\\(NO-\\)?PACKAGES\\][ ]*\n? tpl) (setq rpl (if (or (match-end 1) (not
pkg)) (org-latex-packages-to-string pkg snippets-p t)) tpl (replace-match
rpl t t tpl)) (if pkg (setq end (concat end \n (org-latex-packages-to-string
pkg snippets-p) (if (string-match \\[\\(NO-\\)?EXTRA\\][ ]*\n? tpl)
(setq rpl (if (or (match-end 1) (not extra)) (concat extra \n)) tpl
(replace-match rpl t t tpl)) (if (and extra (string-match \\S- extra)) (setq
end (concat end \n extra (if (string-match \\S- end) (concat tpl \n
end) tpl))
org-splice-latex-header(nil (( fixltx2e nil) ( graphicx t) (
longtable nil) ( float nil) ( wrapfig nil) ( soul t) (
marvosym t) ( wasysym t) ( latexsym t) ( amssymb t) (
hyperref nil) \\tolerance=1000 ( listings) ( xcolor)) ((AUTO
inputenc t) (T1 fontenc t) ( textcomp t)) nil
\\lstdefinelanguage{org}{%\nmorekeywords={:results, :session, :var, :noweb,
:exports},\nsensitive=false,\nmorestring=[b]\,\nmorecomment=[l]{\\#},\n}\n\\lstdefinelanguage{dot}{%\nmorekeywords={graph},\nsensitive=false,\n}\n\\lstset{%\nextendedchars=false,\ninputencoding=utf8x,\n%\nmathescape=false,\nescapechar=`,
% allow escaping to (La)TeX mode within
`..`\ncolumns=flexible,\nkeepspaces=true,\n%\nliterate=\n{á}{{\\'a}}1\n{à}{{\\`a}}1\n{â}{{\\^a}}1\n{ä}{{\\\a}}1\n{é}{{\\'e}}1\n{è}{{\\`e}}1\n{ê}{{\\^e}}1\n{ë}{{\\\e}}1\n{í}{{\\'i}}1\n{ì}{{\\`i}}1\n{î}{{\\^i}}1\n{ï}{{\\\i}}1\n{ó}{{\\'o}}1\n{ò}{{\\`o}}1\n{ô}{{\\^o}}1\n{ö}{{\\\o}}1\n{ú}{{\\'u}}1\n{ù}{{\\`u}}1\n{û}{{\\^u}}1\n{ü}{{\\\u}}1\n})
(org-e-latex--guess-inputenc (org-splice-latex-header document-class-string
org-export-latex-default-packages-alist org-export-latex-packages-alist nil
(plist-get info :latex-header-extra)))
(let* ((header (nth 1 (assoc class org-e-latex-classes)))
(document-class-string (and (stringp header) (if class-options
(replace-regexp-in-string ^[]*documentclass\\(\\[.*?\\]\\)
class-options header t nil 1) header (org-e-latex--guess-inputenc
(org-splice-latex-header document-class-string
org-export-latex-default-packages-alist org-export-latex-packages-alist nil
(plist-get info :latex-header-extra
(org-element-normalize-string (let* ((header (nth 1 (assoc class
org-e-latex-classes))) (document-class-string (and (stringp header) (if
class-options (replace-regexp-in-string ^[
]*documentclass\\(\\[.*?\\]\\) class-options header t nil 1) header
(org-e-latex--guess-inputenc (org-splice-latex-header document-class-string
org-export-latex-default-packages-alist org-export-latex-packages-alist nil
(plist-get info :latex-header-extra)
(let ((class (plist-get info :latex-class)) (class-options (plist-get info
:latex-class-options))) (org-element-normalize-string (let* ((header (nth 1
(assoc class org-e-latex-classes))) (document-class-string (and (stringp
header) (if class-options (replace-regexp-in-string ^[
]*documentclass\\(\\[.*?\\]\\) class-options header t nil 1) header
(org-e-latex--guess-inputenc (org-splice-latex-header document-class-string
org-export-latex-default-packages-alist org-export-latex-packages-alist nil
(plist-get info :latex-header-extra))
(concat (and (plist-get info :time-stamp-file) (format-time-string %%
Created %Y-%m-%d %a %H:%M\n)) (let ((class (plist-get info
Re: [O] new (LaTeX) exporter and date formatting
Hello Nicolas, Nicolas Goaziou wrote: Andreas Leha andreas.l...@med.uni-goettingen.de writes: Ideally, in my opinion, the LaTeX-exporter would honor the #+LANGUAGE: XX setting and change the babel-settings accordingly That seems reasonable. Is there any translation table between language symbols and Babel options? Not that I am aware of. But we could start one quite easily. I got this list of LaTeX-babel supported languages from http://www.tug.org/texlive/Contents/live/texmf-dist/doc/generic/babel/babel.pdf: (just a quick hack...) The following patch should add the language option according to LANGUAGE keywords if babel package is explicitly loaded in preamble. I think this will be a great addition! Is it what you had in mind? I'm a bit reluctant to load babel package if not present. At first sight, I had no particular opinion about whether it's better to load or not Babel by default. After thinking about it, I think you're right NOT loading it by default. Babel plays with cat codes for `:' among others, and can conflict with isodate IIRC. Hence, better let the user decide to really include it or not. Best regards, Seb -- Sebastien Vauban
[O] Stupid questions. this time: org-protocol
Hey guys, Maybe there can be a subject-line label just for me: [O:sq] because I have a million of them. I really don't want to clutter up the list, though. I haven't used org-protocol yet. I've been staying away from it because it uses emacsclient, and my experience has caused me to dislike emacsclient. Will org-protocol work out of the box with gnuclient? Thanks, sorry for the noise.
Re: [O] on the go capture
I use Toodledo (http://toodledo.com). I've been working on org-toodledo.el that syncs todo items between an org file and the toodledo server. There are multiple other toodledo clients including one for the iPhone / iPad that work nicely. The system works pretty well for my needs (todo list management). I do most of my work in org-mode, and use toodledo mostly just for the mobile use case (or remote when I don't have my computer). The project is up on git: https://github.com/christopherjwhite/org-toodledo ...cj On 6/13/12 1:00 PM, Sample Hampton wrote: Users, What do you use to capture when away from orgmode (in the car, on the subway) and what system do you use to migrate those captures into orgmode? Right now I just use a notebook and a pen--and it works fairly well--but moving from notebook to org is certainly a pain, and I am sure I am losing information. What do you use? And if you use mobileorg, then how well does it work? Thanks, Sample
[O] The best way to keep up-to-date with new features?
If you have read the manual, what is the best way to keep up-to-date with new features?, DiffPDFbetween the manual that was read and latest manual? Best wishes, Enda
[O] essentially turn off font-lock except for headings
How do you essentially turn off font-lock except for headings? Best wishes, Enda P.S. like Can there be an #+OPTION to stop comments and weblinks from being coloured and names of directories from being italised, /etc/ ?
Re: [O] emacs --batch without calling all the .el scripts
Enda writes: emacs --batch --visit=index.org --funcall org-export-as-html-batch all the .el scripts in /etc/emacs/site-start.d/ get called which takes time, since all of these are unnecessary except 50org-mode.el, is there is way to only load 50org-mode.el Bastien writes: Untested: emacs -Q --batch --visit=index.org -l \ /etc/emacs/site-start.d/50org-mode.el \ --funcall org-export-as-html-batch HTH, This worked: emacs -Q --batch --visit=index.org --funcall org-export-as-html-batch It did not require the -l /etc/emacs/site-start.d/50org-mode.el. Best wishes, Enda
Re: [O] white (hide)stars in black background terminal
From: Bastien b...@gnu.org To: Enda enda...@yahoo.com Cc: emacs-orgmode@gnu.org emacs-orgmode@gnu.org Sent: Wednesday, June 6, 2012 7:31 PM Subject: Re: white (hide)stars in black background terminal Hi Enda, Enda enda...@yahoo.com writes: When I open org-mode with hidestars in a TTY terminal I cannot see the stars, however when I open them in a terminal emulator inside GNOME, the stars that are supposed to be hidden are white (on a black background). Please share elements of your configuration that are relevant to this issue. Do you experience the same with emacs -Q (no configuration)? This still happens with emacs -Q. Best wishes, Enda
[O] How can I set an event to occur every day except Saturday and Sunday between two given dates?
I know how can I set an event to occur every day except Saturday and Sunday ** Daily meeting %%(memq (calendar-day-of-week date) '(1 2 3 4 5)) How can I set an event to occur every day except Saturday and Sunday between two given dates? Best wishes, Enda
Re: [O] How can I set an event to occur every day except Saturday and Sunday between two given dates?
apologies -- neglected to include the list. Start of forwarded message From: li...@johnrakestraw.com To: Enda enda...@yahoo.com Subject: Re: [O] How can I set an event to occur every day except Saturday and Sunday between two given dates? Fcc: ~/spool/sent.spool Bcc: homes...@johnrakestraw.com, mobiles...@johnrakestraw.com Date: Thu, 14 Jun 2012 13:04:37 -0400 Hi, Enda -- %%(memq (calendar-day-of-week date) '(1 2 3 4 5)) How can I set an event to occur every day except Saturday and Sunday between two given dates? org-class should do what you want -- http://orgmode.org/worg/org-faq.html#org-class --John End of forwarded message
Re: [O] on the go capture
Sample Hampton zaphod4...@aol.com writes: Users, What do you use to capture when away from orgmode (in the car, on the subway) and what system do you use to migrate those captures into orgmode? Right now I just use a notebook and a pen--and it works fairly well--but moving from notebook to org is certainly a pain, and I am sure I am losing information. What do you use? And if you use mobileorg, then how well does it work? Thanks, Sample I tried mobileorg (for Android) when it was first made available but it didn't suit me and I didn't particularly like my Android phones in any case :( I use a Nokia N900 (maemo, aka linux) or Nokia E7 (Symbian) these days, both of which have real keyboards. In either case, I simply ssh to my desktop and run emacs in screen to take notes. With screen, I can have an instance of emacs running constantly which I can access very quickly. -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.1.50.1 and Org release_7.8.11-69-ga2fd96
Re: [O] Using Org for a dissertation
Rasmus ras...@gmx.us writes: Eric Schulte eric.schu...@gmx.com writes: 1) Section labels and other in-document references. It's nice that Org generates these on export, but I need to be able to assign and use labels that will not change if the document is reordered. I know I can simply add such labels via a \label command, but I am worried that using them in addition to Org's autogenerated labels might cause numbering problems in LaTeX. I've not run into any such problems. I tend to construct all of my labels through Org-mode (which works well for export to both HTML and LaTeX). Could you describe how to do section links and references from within Org. I have tried to figure this out for a while now. The only solution I can find (on Worg) depends on precise section names, which is not so stable. I use the new latex export engine The attached is a simple example which works for latex. * Introduction # intro This is some introductory text. * Background In section [[latex:ref][intro]], we introduced the topic. -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.1.50.1 and Org release_7.8.11-69-ga2fd96
Re: [O] Bug: Line breaks in exported LaTeX code [7.8.11]
Uffe Høgsbro Thygesen u...@aqua.dtu.dk writes: Hi Eric Thanks! No, I hadn't thought of that, silly me. It turns out that the following line in my .emacs caused the problems: (add-hook 'LaTeX-mode-hook 'longlines-mode) Interesting. I do not understand why longlines-mode should cause this problem. However, this mode has always had quirky behaviour. You may wish to use visual-line-mode instead which works similar to longlines-mode but better, IMO. -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.1.50.1 and Org release_7.8.11-69-ga2fd96
[O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables
Do you think that you can provide some lisp code that builds the buffer contents and the display properties for the three options that ou refered to as an illustration? I tried inserting tabs into the buffer before the vertical bars, but after reordering it still didn't come out right. Regards, Dov On Thu, Jun 14, 2012 at 6:10 AM, Eli Zaretskii e...@gnu.org wrote: Date: Wed, 13 Jun 2012 22:26:35 +0300 From: Dov Grobgeld dov.grobg...@gmail.com Imagine you have a buffer with the following logical contents (using the convention that capitals are RTL characters). | abcdef | abc | | ABCDEF | ABC | I would like this to be displayed as: | abcdef | abc | | FEDCBA | CBA | The problem is that I want to each column of the table to be isolated (with regards to bidi influence) from other columns in the table. (Of course we also want to choose the table direction, but that is a different and solvable issue.) If there is no such separation, which is the behaviour currently get in emacs HEAD, then the resulting rendered buffer is: | abcdef | abc | | CBA | FEDCBA | Is this even solvable in the current emacs bidi model? Yes, it is. The solution involves putting segment separators between the table columns. These could be TAB characters or a display property whose value is (space . :width N) or (space . :align-to COL). Org maintainers, please ask if you need help in fixing this.
[O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables
Date: Thu, 14 Jun 2012 21:10:46 +0300 From: Dov Grobgeld dov.grobg...@gmail.com Cc: 11...@debbugs.gnu.org Do you think that you can provide some lisp code that builds the buffer contents and the display properties for the three options that ou refered to as an illustration? I tried inserting tabs into the buffer before the vertical bars, but after reordering it still didn't come out right. ??? What exactly did you try? You need to have a TAB before and after each '|' that's between the cells (the outer ones do not need a TAB). Like this (you should see this correctly in Emacs 24.1; move cursor with C-f to see the logical order): | אבגד| הוזחטי | Isn't this what you wanted? As for the display properties, replace the TABs in the example above with something like this: (insert (propertize '(display (space :align-to 10 The number 10 should be the column where you want the | separator to be aligned. For the replacement of the second TAB, increment the value to get the desired alignment of the text of the second cell.
[O] bug#11710: 24.1.50; Bidi attributes are not exported in org-mode html output
Date: Thu, 14 Jun 2012 21:20:17 +0300 From: Dov Grobgeld dov.grobg...@gmail.com When using bidi (bi-direction) reordering together with org-mode, all paragraphs automatically become either RTL or LTR according to the emacs' Bidi heuristic algorithm. Did you customize Emacs to dynamically determine the paragraph direction in Org buffers? By default they are forced to be left-to-right. But when exporting to HTML, the resolved paragraph direction is not included. In HTML the paragraph directions must be set explicitly, e.g. by div dir=RTL.../div, and they should be set according to the directions resolved by emacs. To the Org maintainers: the resolved paragraph direction at character position N in the current buffer can be retrieved like this: (save-excursion (goto-char N) (current-bidi-paragraph-direction))
Re: [O] New Link Syntax: Adding ATTRIBUTES (Was: org-e-html: Including ATTR_HTML)
Hello Nicolas, Many thanks for expanded clarity, and a new direction. On Thu, Jun 14, 2012 at 2:51 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: I understand your problem, but inserting ATTR_HTML keywords in a paragraph isn't possible anymore. I cannot allow that as it would defeat a fundamental change in the new Org syntax. This is good. While not familiar with the details, I clearly see the value of maintaining the logical integrity of the new architecture. ATTR_HTML could ... accept a list of properties that would be applied in order to each link in the paragraph. But it wouldn't scale well... Agreed; this is not the way to go. I'm open to any other suggestion. For example, link's syntax could be extended to allow attributes. I like this idea, and think it is the way to go. -- One approach would be to expand the current link syntax from TWO to THREE pairs of square brackets. Current syntax: http://orgmode.org/org.html#Link-format New syntax: [[link]] [[link][description]] [[link][description][ATTRIBUTES]] Description and attributes would be optional. ATTRIBUTES would consisting of name:value pairs, perhaps giving names export-type prefixes, such as HTML_STYLE and HTML_TITLE, or LATEX_PDFBORDER and LATEX_URLCOLOR. HTML ATTRIBUTES would map to HTML 'attributes': http://www.w3.org/TR/html5/section-index.html#attributes-1 LATEX ATTRIBUTES would map to Latex \hypersetup 'options': http://en.wikibooks.org/wiki/LaTeX/Hyperlinks#.5Chyperref (Subsection: Customization) -- This would be a significant change, but it would make LINKS first class objects, and allow Org mode users to directly apply rich families of link attributes/options. The Manual should then indicate that ATTR_HTML is a /paragraph/-level mechanism, and is no longer intended for use with links: http://orgmode.org/org.html#Links-in-HTML-export There may, of course, be different/better solutions. Thanks for continuing to move this forward! -BC
Re: [O] New Link Syntax: Adding ATTRIBUTES
William Crandall bc3141...@gmail.com writes: Hello Nicolas, Many thanks for expanded clarity, and a new direction. On Thu, Jun 14, 2012 at 2:51 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: I understand your problem, but inserting ATTR_HTML keywords in a paragraph isn't possible anymore. I cannot allow that as it would defeat a fundamental change in the new Org syntax. This is good. While not familiar with the details, I clearly see the value of maintaining the logical integrity of the new architecture. ATTR_HTML could ... accept a list of properties that would be applied in order to each link in the paragraph. But it wouldn't scale well... Agreed; this is not the way to go. I'm open to any other suggestion. For example, link's syntax could be extended to allow attributes. I like this idea, and think it is the way to go. -- One approach would be to expand the current link syntax from TWO to THREE pairs of square brackets. Current syntax: http://orgmode.org/org.html#Link-format New syntax: [[link]] [[link][description]] [[link][description][ATTRIBUTES]] Description and attributes would be optional. ATTRIBUTES would consisting of name:value pairs, perhaps giving names export-type prefixes, such as HTML_STYLE and HTML_TITLE, or LATEX_PDFBORDER and LATEX_URLCOLOR. HTML ATTRIBUTES would map to HTML 'attributes': http://www.w3.org/TR/html5/section-index.html#attributes-1 LATEX ATTRIBUTES would map to Latex \hypersetup 'options': http://en.wikibooks.org/wiki/LaTeX/Hyperlinks#.5Chyperref (Subsection: Customization) -- This would be a significant change, but it would make LINKS first class objects, and allow Org mode users to directly apply rich families of link attributes/options. The Manual should then indicate that ATTR_HTML is a /paragraph/-level mechanism, and is no longer intended for use with links: http://orgmode.org/org.html#Links-in-HTML-export There may, of course, be different/better solutions. Thanks for continuing to move this forward! -BC Is Samuel Wales' extensible syntax proposal germane? http://article.gmane.org/gmane.emacs.orgmode/10204/match=link+syntax All the best, Tom -- Thomas S. Dye http://www.tsdye.com
