[Orgmode] searchable refcard?
Greetings, I can't search the PDF version of the org-mode refcard (in a couple of different apps on Mac OS X). I can match single-character strings, and it appears that my reader apps see spaces between e v e r y s i n g l e c h a r a c t e r, which causes my trouble. (Not a typical problem I have with these apps.) Is a more search-friendly version, or the (presumably LaTeX) source, of the refcard available? Cheers, Nathaniel [please include me ( [EMAIL PROTECTED] ) on any replies, as I'm not a member of this list] ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] searchable refcard?
Sebastian, Thanks for the link to the refcard source. The s p a c e s problem only arose when I used the tex--dvi--ps--pdf route in landscape geometry; portrait geometry didn't have this problem, but of course the text didn't fit the paper size, either. pdftex worked just fine, after I added \pdfpageheight 8.5in \pdfpagewidth 11.0in to the .tex file to get landscape geometry. The idea of an org reference in org-mode sounds useful. Thanks for the file, Alan. --Nathaniel On Thu, Nov 27, 2008 at 4:07 AM, Sebastian Rose [EMAIL PROTECTED]wrote: Hi Nathaniel, I don't know what causes this trouble, but I faced this sometimes with LaTeX generated PDFs. Might be an encoding problem or what ever. The LaTeX sources are available at repo.or.cz, as is the entire Org-mode package: http://repo.or.cz/w/org-mode.git?a=blob;f=doc/orgcard.tex;h=8e2cbe0d76f9b71997c106982911b144ed5eff2f;hb=HEAD Regards, Sebastian Nathaniel Cunningham [EMAIL PROTECTED] writes: Greetings, I can't search the PDF version of the org-mode refcard (in a couple of different apps on Mac OS X). I can match single-character strings, and it appears that my reader apps see spaces between e v e r y s i n g l e c h a r a c t e r, which causes my trouble. (Not a typical problem I have with these apps.) Is a more search-friendly version, or the (presumably LaTeX) source, of the refcard available? Cheers, Nathaniel [please include me ( [EMAIL PROTECTED] ) on any replies, as I'm not a member of this list] ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode -- Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover Tel.: +49 (0)511 - 36 58 472 Fax: +49 (0)1805 - 233633 - 11044 mobil: +49 (0)173 - 83 93 417 Email: s.rose emma-stil de, sebastian_rose gmx de Http: www.emma-stil.de ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [O] Org-mode latex pdf export issue: Underlined lines not breaking properly
Suvayu Ali fatkasuvayu+linux at gmail.com writes:
Org mode
translates _underlined text_ to \underline{underlined text}, however if
you read the TeX.sx question referenced below you will see that it
doesn't support line breaks and the TeX community recommends \uline{..}
from the ulem package.
http://TeX.stackexchange.com/a/13382/4416
The \ul{..} command from the soul package also supports underlining across
line breaks.
*And soul is included by default in org's list of loaded latex packages* -- see
org-latex-default-packages-alist.
Therefore it would be painless for org users if \underline in
org-latex-text-markup-alist were replaced with \ul -- and it would provide
more complete support of underlining!
Thanks,
Nathaniel
[O] orgstruct: broken global visibility cycling, when in comments
I'm attempting to use orgstruct minor mode in emacs-lisp-mode (org 8.0.3 in recent Aquamacs and in vanilla Emacs 24.3.1). I find: - cycling an individual headline using tab key works fine - global cycling via S-Tab (when on a headline) to more expanded visibility (e.g. OVERVIEW -- CONTENTS or CONTENTS -- SHOW ALL) works fine - global cycling via S-Tab (when on a headline) to more limited visibility fails without error (echo area still reports OVERVIEW or CONTENTS, etc.) I have orgstruct-heading-prefix-regexp set to ^;;. Example buffer contents that fail global cycling to narrower scope: ;; Testcase for orgstruct-mode in emacs-lisp-mode ;;* top level headline 1 ;;** 2nd level headline A (setq var2 value2) ;;** 2nd level headline B (setq var3 value3) ;;** 2nd level headline C (setq var4 value4) ;;* top level headline 2 (setq var5 value5) I find no trouble with global cycling if I remove the ;; comment characters in all headlines and set orgstruct-heading-prefix-regexp to nil. I suspect this is a bug; but perhaps I'm doing something wrong? Thanks for any help. Cheers, Nathaniel
Re: [O] orgstruct: broken global visibility cycling, when in comments
Thanks to Christopher Schmidt for solving my problem: On Fri, Jun 14, 2013 at 11:30 PM, Nathaniel Cunningham nathaniel.cunning...@gmail.com wrote: I'm attempting to use orgstruct minor mode in emacs-lisp-mode (org 8.0.3 in recent Aquamacs and in vanilla Emacs 24.3.1). I find: - cycling an individual headline using tab key works fine - global cycling via S-Tab (when on a headline) to more expanded visibility (e.g. OVERVIEW -- CONTENTS or CONTENTS -- SHOW ALL) works fine - global cycling via S-Tab (when on a headline) to more limited visibility fails without error (echo area still reports OVERVIEW or CONTENTS, etc.) I have orgstruct-heading-prefix-regexp set to ^;;. Note that this value for the prefix (actually the version with a space, ^;; ) is suggested by the Org manual for version 8.0.3 Christopher pointed out that orgstruct-mode implicitly starts the real regexp that is used for headline matching with a ^. Your additional ^ breaks the regexp. I verify that setting orgstruct-heading-prefix-regexp to ;; (or ;; with a space) solves the problem. Thank you Christopher! --Nathaniel
[O] repeated underscores and subscript woes
Hello,
I use org-mode (currently v7.9.3) to build materials for the courses I
teach. I tend to use repeated underscores to indicate a blank, e.g.:
1) Fill in the ___.
Unfortunately, org-mode treats these as *successive* subscript requests,
and the text that follows is severely disrupted when exported via LaTeX.
The local or global setting of `org-export-with-sub-superscripts' does not
seem to affect this behavior.
It seems appropriate that:
- no subscripting should occur in the above case
when `org-export-with-sub-superscripts' is set to nil or {}; and
- repeated underscores without any braces should probably not ever trigger
subscripting on export.
Thanks for all the continued work on org-mode!
--Nathaniel
[O] How to markup verbatim code including = and ~?
I'd like to incorporate some scraps of code in an org file. These scraps include both ~ and =, the markers for verbatim text and code. I used customize-variable org-emphasis-alist to change the symbols to mark verbatim text, but without success; adding unusual symbols broke LaTeX export of the org file, and swapping the underline and verbatim symbols had no effect (code marked _like so_ was still underlined instead of made verbatim). Advice would be appreciated! Thanks, Nathaniel p.s. I don't subscribe to this list, so please include my email in reponses. Thanks!
Re: [O] How to markup verbatim code including = and ~?
Alright, I solved my own problem. I was able to get verbatim working with a unicode symbol (√) as delimeter, by editing both org-emphasis-alist and org-export-latex-emphasis-alist. Cheers! --Nathaniel On Sat, Mar 2, 2013 at 5:05 PM, Nathaniel Cunningham nathaniel.cunning...@gmail.com wrote: I'd like to incorporate some scraps of code in an org file. These scraps include both ~ and =, the markers for verbatim text and code. I used customize-variable org-emphasis-alist to change the symbols to mark verbatim text, but without success; adding unusual symbols broke LaTeX export of the org file, and swapping the underline and verbatim symbols had no effect (code marked _like so_ was still underlined instead of made verbatim). Advice would be appreciated! Thanks, Nathaniel p.s. I don't subscribe to this list, so please include my email in reponses. Thanks!
