Tim Cross writes:
> You do need to be careful when sharing your .emacs.d between machines to
> ensure you use something like gitignore to exclude things you may not
> want to share across systems (such as auto-save files, various command
> history files etc).
Yes, that's
I was wondering if there is any simple way of displaying the actual tangled
code in the org-mode buffer and resulting exports. One can #+INCLUDE the
resulting file, seeing it in the export; one can M-x ffap the #+INCLUDE file to
see it in a buffer; one can do a hack like shelling out and
On Mon, 24 Apr 2017, Jeremie Juste wrote:
Hello,
I would like to use :prologue and epilogue with latex output when using
R. Would it be possible to do something like the following?
[...]
#+BEGIN_SRC R :results output latex :prologue \\begin{table} :epilogue
\\end{table} [...]
[...]
You do need to be careful when sharing your .emacs.d between machines to
ensure you use something like gitignore to exclude things you may not
want to share across systems (such as auto-save files, various command
history files etc). I've found the use of use-package and init.el in a
git repo the
Have a look at the use-package package. I have found it makes this much
easier. There are some complications associated with using it and
org-mode, due mainly to emacs being bundled with one version and another
vesion being available in both the gnus and org-mode elpa
repos. However, once you
Hello,
I would like to use :prologue and epilogue with latex output when using
R. Would it be possible to do something like the following?
#+NAME: test1123
#+BEGIN_SRC R :results output latex :prologue \\begin{table} :epilogue
\\end{table} :session *R* :dir tmp :cache no
I find that the best way is to store the entire ~/.emacs.d directory
(including the /elpa subdirectory) in a git repository. This makes it
easy to keep your entire config in sync between machines, and it means
you keep your init file in sync with the versions of packages.
Otherwise you may find
Hi Ian,
Don't have time to dig into this at the moment, but it sounds very
impressive and useful. I look forward to giving it a try soon. Keep up
the good work!
Eric S Fraga writes:
> On Monday, 10 Apr 2017 at 12:03, Alan Schmitt wrote:
>> Hello,
>>
>> I'm having `bibtex-parse-buffers-stealthily' fail when there is an
>> org-mode buffer with a bibtex source block. For instance, if you have
>> the following block in an org file
>
> I
Hi,
This is more of a general emacs question.
I often use the same .emacs on various machines which may not have all
the packages I normally load. To get around this I use the Fabrice
Niessen's 'try-require' function taken from
http://www.mygooglest.com/fni/dot-emacs.html
Due to some recent
Nick Dokos writes:
> "Loris Bennett" writes:
>
>> "Loris Bennett" writes:
>>
>>> "Loris Bennett" writes:
>>>
Hi,
I'm interested in exporting from Org to Foswiki format. Is
On Wednesday, 19 Apr 2017 at 21:33, Adam Porter wrote:
> Inline tasks are now skipped. Thanks!
Excellent. Thanks!
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50, Org release_9.0.5-444-g998576
signature.asc
Description: PGP signature
On Monday, 10 Apr 2017 at 12:03, Alan Schmitt wrote:
> Hello,
>
> I'm having `bibtex-parse-buffers-stealthily' fail when there is an
> org-mode buffer with a bibtex source block. For instance, if you have
> the following block in an org file
I also get this and, although it doesn't really affect
* lisp/ob-C.el (org-babel-C-execute): Made sure name of compiled
program is converted to local representation before sending it to the
shell on remote host.
The problem was when one would try to evaluate C source code block in
the file on remote host. Compilation would go normally, then
14 matches
Mail list logo