On Thursday, 23 Feb 2023 at 16:25, Rob Sargent wrote:
> Looks to me like this only happens if the last word of the line is
> "emphasized" and larger font.
This is not an org problem; it's LaTeX. It's happening because LaTeX
has a problem breaking up the line at the previous word. You can help
La
Damien Cassou writes:
> I've signed the FSF copyright agreement in the context of my
> contributions to Emacs. Do I need to do any more paperwork?
No, you don't.
Bastien, could you please check FSF records?
>> I think that it will be a good idea to indicate in the `message' where
>> the error i
Ihor Radchenko writes:
> I think you forgot to attach the updated patch :)
typical. I'm so sorry.
--
Damien Cassou
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
>From c116e27a84972f9e12a869f2b4983bb84ee50b15 Mon Sep 17 00:00:00 2001
F
Sébastien Miquel writes:
> What benefits does that bring over making enabled features available in
> =info= for the usual transcoders and advising them ?
We should indeed make the features/condition available via info.
However, advising is (1) bad practice unless we have no choice; (2) not
as f
Fraga, Eric writes on Fri 24 Feb 2023 08:06:
> On Thursday, 23 Feb 2023 at 16:25, Rob Sargent wrote:
> > Looks to me like this only happens if the last word of the line is
> > "emphasized" and larger font.
>
> This is not an org problem; it's LaTeX. It's happening because LaTeX
> has a prob
On Friday, 24 Feb 2023 at 11:42, alain.coch...@unistra.fr wrote:
> Now, is there a way to tell Org to export _=MappingInstruction=_ as
> \ul{\texttt{MappingInstruction}}?
Well, I found I never used strike-through but definitely wanted to be
able to highlight text. So, I redefined the +...+ markup
Ihor Radchenko writes:
However, it will be much harder to add something in the middle of the
exported contents.
I do like the original proposal. The latex preamble is something that
a lot of users will want to modify, and is naturally made of a lot of
concatenated snippets with little interdepe
Hi,
Timothy writes:
Notably, I’ve now got a draft manual entry (see the last patch attached), which
should go a long way to better explaining what this is without asking you to
wade through all the code comments 😄
Thank you for sharing your work Timothy, I've been using your export
features fo
Hello everyone,
I used Org-mode for taking notes in some school lessons, but it was a
bit chaotic. I try to make it more efficient, easy to navigate and
manage.
I would like to know if you have any advice or suggestions.
Here, I will explain what I need, what I think to do this semester and
wher
Sébastien Miquel writes:
> I think it would be useful to support an easy way to toggle a feature
> on and off. Either the manual should describe the best way to make a
> feature depend on a user variable (this requires using the #+BIND
> keyword, I guess), or I'd like org to support a new keyword
Sébastien Miquel writes:
> For most changes, you'll have to copy and modify the original
> transcoder's implementation anyway. At this point, you might as well
> write the feature logic in lisp (checking features through =info=),
> instead of your `transcoder-conditions`.
Consider the feature re
You are welcome.
I also discovered just now that you can do C-u C-u C-c C-l to skip storing
functions that are not part of org-core.
If anyone knows how to use store functions that do not clobber the build in
ones, I would be happy to update org-ref so you can use all the link store
options.
On
* ob-screen.el: (org-babel-execute:screen): Parse header params
for `:var', then inject into screen session.
(org-babel-variable-assignments:screen): Copied from
ob-shell.el org-babel-variable-assignments:shell
* etc/ORG-NEWS: Document as New Feature
This change only supports single-value varia
Sébastien Gendre writes:
> Hello everyone,
>
> I used Org-mode for taking notes in some school lessons, but it was a
> bit chaotic. I try to make it more efficient, easy to navigate and
> manage.
I used org notes heavily through more than two school degrees, and loved it.
Definitely a sweet-spot
Dear all,
How to do it:
My org-latex-preview related config:
```
(with-eval-after-load 'org
(add-to-list 'org-latex-packages-alist '("" "stmaryrd" t))
(add-to-list 'org-latex-packages-alist '("" "tikz-cd" t))
(add-to-list 'org-latex-packages-alist '("" "thisisastupidtestfile" t
Hi Chris,
> Note: I haven’t been able to compute the return value of the hash function for
> my latex expression, because I can’t figure out what the arguments actually
> are,
> specifically `forbuffer`, `fg` and `bg`, but the above reasoning seems sound.
> Note: Removing specifically the images
On Friday, 24 February 2023 18:49:10 CET Timothy wrote:
> Hi Chris,
>
> > Note: I haven’t been able to compute the return value of the hash function
> > for
> > my latex expression, because I can’t figure out what the arguments actually
> > are,
> > specifically `forbuffer`, `fg` and `bg`, but t
I realize the patch should be an attachment, not the body of the email. Sorry.
R-sending as attachment.
-k.
>From 5a4707cc16fb5f10cd394762f41d50d8830db240 Mon Sep 17 00:00:00 2001
From: "Kenneth D. Mankoff"
Date: Mon, 20 Feb 2023 21:40:39 -0800
Subject: [PATCH] lisp/ob-screen.el: Support ~:v
Ihor Radchenko writes:
Consider the feature request from the past about wrapping/prepending
to exported headings:
* Heading1
* Heading2
:PROPERTIES:
:LATEX_TEMPLATE: (:snippet "\clearpage" :order -100)
:END:
# This Heading2 will start on a new page
If we implement export transcoders as much as
Ihor Radchenko writes:
I think it would be useful to support an easy way to toggle a feature
on and off. Either the manual should describe the best way to make a
feature depend on a user variable (this requires using the #+BIND
keyword, I guess), or I'd like org to support a new keyword, such as
I don't know if this can be considered a bug or if I'm trying to do
something not supported.
Create an .org file with the following contents:
* First Level
** One :tag:
*** Child
** Two
** Three
** Four :tag:
** Five
Now, C-c / m (or M-x org-sparse-tree and select m) and Match: tag.
The resulti
Hello,
I was trying to export an .org file to .rst. I have ox-rst 20200815.1511
installed, and I have run (require 'ox-rst), but despite this, there is
no option for rsT in the Org Export Dispatcher. Did I miss something to
make it work?
Emacs version: 28.2
Orgmode verion: 9.1.3
Thanks,
--
Ánge
Okay, today I did some research and found that every "C-c
C-" binding is used in Org Mode except for "C-c C-g".
While that one is technically reserved for the mode's use, I
suspect the reason it's unbound is that people are accustomed to
using C-g as a quit command (and they get that effect if
Hi Sebastien,
> I think it would be useful to support an easy way to toggle a feature
> on and off. Either the manual should describe the best way to make a
> feature depend on a user variable (this requires using the #+BIND
> keyword, I guess), or I’d like org to support a new keyword, such as
>
On 25/02/2023 01:33, Ken Mankoff wrote:
Subject: [PATCH] lisp/ob-screen.el: Support ~:var~ header args for babel
blocks
Thank you for the patch. I suppose, suggestion to send patches as
attachments is added mostly to prevent patches inside HTML message body.
If a message could be feed to "gi
I'll make only a small comment here. I've used Emacs/Org for classes
that I take at University of Hawai`i (they have a wonderful program to
allow us old people to attend class for free). I do one directory per
class and one org-mode file per class inside that directory, where
attachments (papers,
26 matches
Mail list logo
