Hello,
Kaushal Modi writes:
> I am not an HTML expert. But recently off-list, I learnt that and
> tags aren't recommended to be used for styling any more (for a while now).
>
> Instead and should be used respectively.
>
> If there are no objections, I can commit this little change to the mas
Garreau, Alexandre writes:
> Why is there no syntax highlighting for *inline* source/code blocks?
>
> For instance, if I type the following:
>
> #+BEGIN_SRC org
> src_emacs-lisp{(foo bar (quux))}
> #+END_SRC
>
> The underscore is not displayed, “emacs” is displayed in face
> ~org-latex-and-re
Dear Org-Mode Developers,
I was missing convert-region functions in the ox-ascii export back-end
as are provided by the HTML, LaTeX, Texinfo, and MarkDown back-ends [1],
and hence crafted my own (copied below) to go into my init file. My use
case is composing emails using notmuch-message-mode.
[1
Nicolas Goaziou writes:
>> ;; I tried to add this, but failed. because `coderef` is executed in
>> `org-edit-src-code` which invokes `org-src--edit-element`, it create a
>> dedicated buffer which does not have `buffer-file-name`. I don't know how to
>> archive what I want now.
>>
Hello,
I am not an HTML expert. But recently off-list, I learnt that and
tags aren't recommended to be used for styling any more (for a while now).
Instead and should be used respectively.
If there are no objections, I can commit this little change to the master
branch.
References:
- https
i duly saved this macro, didn't think to look for it, and used datefudge(1).
Matt Price writes:
> On Tue, Oct 23, 2018 at 2:32 PM John Kitchin
> wrote:
>
>> I think that what you really want to do here is modify org-mime-compose so
>> that you can use the send-actions argument to message-mail. In
>> scimax-email.el I use that to be able to turn an org-heading into an e
Dear Chuck,
Thanks for suggesting xtables. I have used it in the past, but had more
or less forgotten about it. I'll give it a try again.
Best regards,
Lennart.
On 22-10-18 18:42, Berry, Charles wrote:
>
>
>> On Oct 22, 2018, at 7:43 AM, L.C. Karssen wrote:
>>
>> Dear list,
>>
>> I'd like t
On Tue, Oct 23, 2018 at 3:38 PM Matt Price wrote:
>
>
> On Tue, Oct 23, 2018 at 2:32 PM John Kitchin
> wrote:
>
>> I think that what you really want to do here is modify org-mime-compose
>> so that you can use the send-actions argument to message-mail. In
>> scimax-email.el I use that to be able
On 2018-10-23 at 14:33, John Kitchin wrote:
> There are some answers at
> https://emacs.stackexchange.com/questions/32396/complete-path-numbering-of-org-mode-headlines-and-plain-lists
Interesting. Thank you (I’m unfortunately not very friend with search
engines): that also raises altogether the q
On Tue, Oct 23, 2018 at 2:32 PM John Kitchin
wrote:
> I think that what you really want to do here is modify org-mime-compose so
> that you can use the send-actions argument to message-mail. In
> scimax-email.el I use that to be able to turn an org-heading into an email,
> send it, and then jump
There are some answers at
https://emacs.stackexchange.com/questions/32396/complete-path-numbering-of-org-mode-headlines-and-plain-lists
.
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA
I think that what you really want to do here is modify org-mime-compose so
that you can use the send-actions argument to message-mail. In
scimax-email.el I use that to be able to turn an org-heading into an email,
send it, and then jump back to the heading to insert some information about
the email
Hi,
This is provided on (almost?) all export formats, but yet when looking
at an org-file the prefered way, with emacs, there’s no numbering, by
default.
It’s so useful and simple (using a display text/overlay property), is
there just anything implementing that? mainline? if so why isn’t it?
Hey, I guess this is OT.
I'm trying to advice org-mime-org-buffer-htmlize so that it returns to the
org buffer when its done. I want to do something like this:
(let ((thisbuffer (current-buffer))
(advice-add
'mu4e-sent-handler
:after (lambda (docid props)
(switch-to-buffe
On Tuesday, 23 Oct 2018 at 19:48, stardiviner wrote:
> This is really helpful for me, I use smartparens before, but it is a
> little heavy. So I disabled it. I found your solution is simple and
> fast. I modified a little:
+1
I gave up long ago on smartparens but skeleton seems to work well.
--
Nicolas Goaziou writes:
Hi, sorry for late response, because I'm a little lazy on give effort on
review my patch and improve it again. But now I finished it. Actually I
corrected my patch as soon as you replied email with mentioned. Today I
pick up this task again, and add a new improve which su
Roland Everaert writes:
> Hi,
>
> I use the following configuration:
>
> parenthèses, accolades et brackets ;;
> (setq skeleton-pair t)
> (global-set-key "[" 'skeleton-pair-insert-maybe)
> (global-set-key "{" 'skeleton-pair-insert-maybe)
> (global-set-ke
Why is there no syntax highlighting for *inline* source/code blocks?
For instance, if I type the following:
#+BEGIN_SRC org
src_emacs-lisp{(foo bar (quux))}
#+END_SRC
The underscore is not displayed, “emacs” is displayed in face
~org-latex-and-related~ *and* in subscript display (smaller and
n
Berry, Charles writes:
>
> This works
>
> #+begin_src sh :var encrypted=(org-babel-ref-resolve "base64 encrypt text()")
> echo $encrypted
> #+end_src
>
> You might write a wrapper, so something like (quote-ref "base64 encrypt
> text")will handle it.
>
Thanks very much! this solved m
Hi,
I use the following configuration:
parenthèses, accolades et brackets ;;
(setq skeleton-pair t)
(global-set-key "[" 'skeleton-pair-insert-maybe)
(global-set-key "{" 'skeleton-pair-insert-maybe)
(global-set-key "(" 'skeleton-pair-insert-maybe)
(glob
21 matches
Mail list logo