Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Grant Rettke g...@wisdomandwonder.com writes:
Good evening,
My goal is to obtain the following behavior in org mode for a document:
1) Report an error if there is a source block without a language
specified
2) Report an
Kit-Yan Choi k...@kychoi.org writes:
But is it theoretically possible to have two remote file paths sharing
the same local copy file name? i.e. `make-temp-file' generates the
same temporary file name for two separate calls?
No, never ever. After choosing a random file name, make-temp-file
On 2014-11-29, at 04:48, Jorge A. Alfaro-Murillo wrote:
If you decide to go with LaTeX, the reason to split your
dissertation in several chapters is so that the compilation can
run faster, since when you change a chapter and compile only that
chapter is compiled again. This is a
Dear Org maintainers,
I was using Org to write a software manual with a structure along the
lines of:
* Equations
How to write equations in software FOO.
* Footnotes
How to write footnotes in software FOO.
* Images
How to insert images in software FOO.
When I exported the document (to
Hello,
Is it ok to apply the attached patch? I don't want to break anything.
I want to be able to denote my source blocks like so:
- *~* is the mark,
- *|* is the point
#+begin_src elisp
(~a b c| d e f g h i j k l m n o p q r s t u v w x y z)
#+end_src
- `org-edit-special' will automatically
Hello,
Arni Magnusson arn...@hafro.is writes:
I was using Org to write a software manual with a structure along the
lines of:
* Equations
How to write equations in software FOO.
* Footnotes
How to write footnotes in software FOO.
* Images
How to insert images in software FOO.
Hello,
Oleh ohwoeo...@gmail.com writes:
I want to be able to denote my source blocks like so:
- *~* is the mark,
- *|* is the point
#+begin_src elisp
(~a b c| d e f g h i j k l m n o p q r s t u v w x y z)
#+end_src
- `org-edit-special' will automatically transform this markup into an
Hi Nicolas,
I don't understand what your use-case is. Note that `org-edit-special'
already preserves region.
That's good, but not what I need. I want to go from an unmarked region
in an org file with markup
to a marked region without markup in the *Org Src* buffer.
I've defined a custom
I don't understand what your use-case is. Note that `org-edit-special'
already preserves region.
That's good, but not what I need. I want to go from an unmarked region
in an org file with markup
to a marked region without markup in the *Org Src* buffer.
That still doesn't explain why you
I don't understand what your use-case is. Note that `org-edit-special'
already preserves region.
That's good, but not what I need. I want to go from an unmarked region
in an org file with markup
to a marked region without markup in the *Org Src* buffer.
That still doesn't explain why you
What a treat, sir, thank you for sharing that as if by some delightful
magic, which surely it indeed is.
On Sat, Nov 29, 2014 at 4:38 AM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Grant Rettke g...@wisdomandwonder.com writes:
Hi Henry,
Henry Hirsch he...@w3-net.de writes:
So how can org mode support wrapping sections in html?
Especially for more complex cases where a section or
multiple sections will be wrapped in multiple divs.
You can do this with an export filter or filters. See the Advanced
Configuration
Marcin Borkowski writes:
I mostly agree, but the above is not true: see TeX-pin-region
and TeX-command-region. Bottom line: IMHO no point in dividing
into many files.
You are right, you can compile a region in AUCTeX, or export just
a region in org, but the problem (besides having to
Sure.
I suggest inserting a short paragraph into section 2.2, both in the manual
and the compact guide. Working from today's snapshot of the repository,
the two patches are as follows.
$ diff org-before.texi org-after.texi
1212c1212,1217
@noindent Some people find the many stars too noisy
The location of the second patch (in orgguide.texi) is line 348:
348c348,351
Arni
-- Forwarded message --
Sure.
I suggest inserting a short paragraph into section 2.2, both in the manual
and the compact guide. Working from today's snapshot of the repository,
the two
Grant Rettke g...@wisdomandwonder.com writes:
What a treat, sir, thank you for sharing that as if by some delightful
magic, which surely it indeed is.
Many thanks also from my side!
On Sat, Nov 29, 2014 at 4:38 AM, Nicolas Goaziou m...@nicolasgoaziou.fr
wrote:
Hello,
Andreas Leha
On 2014-11-24, at 19:38, Rasmus wrote:
Marcin Borkowski mb...@wmi.amu.edu.pl writes:
Hello,
I'm writing (in Org) a text on Emacs usage. How to
correctly/canonically represent keystrokes, like C-x RET f?
Currently, I use =C-x RET f=; are there any alternatives?
That's what I'd do. Or
On 2014-11-29, at 22:53, Marcin Borkowski wrote:
On 2014-11-24, at 19:38, Rasmus wrote:
Marcin Borkowski mb...@wmi.amu.edu.pl writes:
Hello,
I'm writing (in Org) a text on Emacs usage. How to
correctly/canonically represent keystrokes, like C-x RET f?
Currently, I use =C-x RET f=; are
On 2014-11-29, at 18:30, Jorge A. Alfaro-Murillo wrote:
Marcin Borkowski writes:
I mostly agree, but the above is not true: see TeX-pin-region
and TeX-command-region. Bottom line: IMHO no point in dividing
into many files.
You are right, you can compile a region in AUCTeX, or export
hi nicolas,
you asked for a reproducible recipe. here it is. i have limited
vertical real estate so i hope this can be fixed! is it an emacs bug
or an org bug?
run this (after substituting in where you keep org maint) and search
for lightly org:
thanks.
samuel
=== call
emacs -Q --geometry
Marcin Borkowski mb...@wmi.amu.edu.pl writes:
On 2014-11-24, at 19:38, Rasmus wrote:
Marcin Borkowski mb...@wmi.amu.edu.pl writes:
Hello,
I'm writing (in Org) a text on Emacs usage. How to
correctly/canonically represent keystrokes, like C-x RET f?
Currently, I use =C-x RET f=; are
21 matches
Mail list logo
