Hello,
Neil Jerram writes:
> I don't think that Scheme output results are correctly handled. Please
> consider:
>
> #+BEGIN_SRC scheme :results output
> (display "a") (newline)
> (display "b") (newline)
> (display "c") (newline)
> '(a b c)
> #+END_SRC
>
>
> #+RESULTS:
Hello,
Jeff Larson writes:
> I think simplest change is that the encryption and decryption
> commands in org-mobile.el need to add the '-md md5' option. So this line
> for encryption:
>
>
Hello,
Christian Garbs writes:
> * ob-vala.el: Add support for the Vala language to Babel.
Thank you. Comments follow.
> +;; file extension
;; File extension.
> +;; header arguments empty by default
;; Header argument empty by default.
> +(defvar
Hello,
Stig Brautaset writes:
> org-drill requires only cl-lib rather than cl, so should use cl-gensym
> rather than gensym I believe.
>
> From 1eef99d550e467bf4a3eaf6bdbe4d3a482f6c187 Mon Sep 17 00:00:00 2001
> From: Stig Brautaset
> Date: Fri, 14 Jul
Hello,
"José L. Doménech" writes:
> Enhance the babel block for scheme.
>
> Allows scheme code blocks to return a table and add a :prologue param
> to the scheme blocks. All :prologue params are prepended to the
> body of code.
>
> * lisp/ob-scheme.el
Hello,
Thiago Alves writes:
> For example, lets say I have this code on my doc (the `|` character is
> the cursor):
>
> #+BEGIN_SRC emacs-lisp
> (setq user-full-name "Thiago Alves"
> user-mail-address "t...@thiagoalves.com.br"|)
> #+END_SRC
>
> With
Hello,
Stig Brautaset writes:
> From ead36e862d150e3a83d363bdead850a2e3ec281d Mon Sep 17 00:00:00 2001
> From: Stig Brautaset
> Date: Fri, 14 Jul 2017 20:43:11 +0100
> Subject: [PATCH 1/3] org-test.el: use prefixed functions from cl-lib.el rather
> than
Hello,
John Morrissey writes:
> I'm syncing to Nextcloud via CalDAV with org-mode 9.0.3 and the latest
> org-caldav.
>
> Events are sometimes synced (and modified in the .org file) with the prefix
> "S:". The symptoms are exactly like:
>
>
Hi,sorry for late response. I like the new docs very much.I would like to suggest some minor changes.
0001-oprg-prtocol-minor-changes-to-new-documentation.patch
Description: Binary data
Kind regardsMario—
Am 06.07.2017 um 19:54 schrieb Nicolas Goaziou :Hello,Mario
John Morrissey writes:
> Hi Nicolas, the behavior I'm observing isn't so much that the .ics is
> incorrect. Instead, it's what happens to the corresponding item in the
> org file.
"ox-icalendar.el" doesn't modify the Org file, except when an ID
property is created.
> For
Seems like the harder I try to be thorough, the more likely I am to mess
something up. The instructions for trying it out were slightly
incorrect, but they're outdated now, anyway. Please see the repo for
current instructions. Thanks.
Hello,
Mario Martelli writes:
> sorry for late response. I like the new docs very much.
>
> I would like to suggest some minor changes.
Thank you for the feedback.
I included your suggestions and pushed the change.
Regards,
--
Nicolas Goaziou
Nikolay Kudryavtsev writes:
> Sorry for kind of resurrecting this thread.
Not at all. :) You might consider filing an issue on the GitHub
tracker, though, because I almost didn't notice this (just haven't been
watching the ml lately).
> I've been trying to get
On Sun, Jul 23, 2017 at 01:38:23PM +0200, Nicolas Goaziou wrote:
> John Morrissey writes:
>
> > I'm syncing to Nextcloud via CalDAV with org-mode 9.0.3 and the latest
> > org-caldav.
> >
> > Events are sometimes synced (and modified in the .org file) with the
> > prefix "S:". The
Hi friends,
I put together another little tool I've been thinking about for a while.
I'm calling it org-super-agenda at the moment, but org-divided-agenda
might be more descriptive; feedback on the name is welcome.
Before I forget and have to have Grant cover for me, you can find it
here:
Hello,
Chunyang Xu writes:
> The following Emacs Lisp code block has multiple expressions. When I try
> to execute it, it fails and says "princ: Invalid function: (a b c)".
>
> #+BEGIN_SRC emacs-lisp :results value pp
> (setq my-list '(a b c))
> my-list
> #+END_SRC
>
>
Hello,
Tyler Smith writes:
> (setq org-latex-listings t
> org-latex-listings-options
> '(("backgroundcolor" "\\color[gray]{0.95}")
This is incorrect. Per "listings" manual, a commend with an optional
argument needs to be included within curly braces:
My org documents include lots of source code blocks, in a variety of
languages. I use the listings package to give each language a
distinctive look.
Lately, my work has involved using shell commands on different machines,
as different users. I'd like to give each shell environment (e.g., local
Hello,
Jay Kamat writes:
> However, it would be nice to add a "using namespace std" to this
> source code block, so it can become:
>
> #+BEGIN_SRC C++ :includes :namespaces std
> cout << "Hello world\n";
> #+END_SRC
>
>
> Which makes it cleaner and easier to read,
Hello,
Anders Papitto writes:
> I have org version 9.0.3 (and I've been noticing this the whole time I've
> used org - only just now reporting it), and this is 100% consistent for me.
>
> I often have two client frames open, connected to the same emacs daemon.
> One
Mario Martelli writes:
> I suppose so, if one knows how to configure URL handlers on their
> OS. Of course there are some things missing from the
> documentation. But it’s more than we have at the moment :)
FYI, I have some instructions for setting up org-protocol at
21 matches
Mail list logo