Hello,
I would like to re-submit this idea, now that I am reasonably sure that
my implementation will not impact users who do not use the feature.
(I understand that Org 9.4 is on the way. I am not asking for this
feature to be included right now; I would like to get some feedback
first, then mo
Hi Nicolas,
On Wed, 24 Jun 2020 at 12:46, Nicolas Goaziou
wrote:
Hello,
Gustavo Barros writes:
You have a good point here. When I made the suggestion I was naively
thinking the featured could be plugged/hooked somewhere in Org, when
fontification is done. But that's not really true, as
> Sorry for being late to the party, but, IMO, this doesn't sound like
> a right approach to the problem of invisible emphasis markers. A user
> choosing to hide emphasis markers should not need to—or even be given
> the opportunity to—display them in order to edit them efficiently.
>
I agree that
Hello,
Gustavo Barros writes:
> You have a good point here. When I made the suggestion I was naively
> thinking the featured could be plugged/hooked somewhere in Org, when
> fontification is done. But that's not really true, as the feature
> requires being run every time the point moves too.
Hello Eric and Nicolas,
I saw from Eric's email that he is using a newer Org release 9.3.7 (I was
on 9.3.6).
I updated to 9.3.7 and exported via latex to pdf and it works perfectly now.
I should have checked for a newer release prior to posting my issue.
Many thanks for your help,
Matthew
On Wednesday, 24 Jun 2020 at 09:46, Matthew Henderson wrote:
> What version of org-mode are you using? I recently updated to 9.3.6 and am
> fairly certain this issue is new.
I've just updated org on my system and description lists work just fine,
as Nicolas has indicated.
--
: Eric S Fraga via E
Hi Shankar,
Detailed comments are up for Kyle, or someone more qualified than
myself, but I leave one further comment regarding the suggestion I had
made.
On Wed, 24 Jun 2020 at 09:53, Shankar Rao wrote:
I agree that adding this functionality as additional options to
org-hide-emphasis-mark
Thanks Nicolas,
What version of org-mode are you using? I recently updated to 9.3.6 and am
fairly certain this issue is new.
I have not compared latex output from previous org-mode versions however
description labels in previous org mode versions were treated correctly by
xelatex(e.g bold font in
Kyle, Gustavo,
Thank you both for your detailed feedback. Attached is a new version of the
patch that incorporates most of your suggestions.
>> I have not yet signed the papers assigning copyright to the FSF. I sent
> a
> >> request for the papers to ass...@gnu.org, but have not yet received a
>
Hi
4 years ago Michael Brand provided the following nice solution, which as
far as I know is still not in master.
(add-hook 'org-export-before-processing-hook 'f-ox-filter-table-column-del)
(defun f-ox-filter-table-column-del (back-end)
"Delete the columns $2 to $> marked as \"/\" on a row
Hello again,
sorry, for the noise. Just minutes after posting the question I
discovered the difference between the org files: they are stored in
different sub-directories. Fixing the path solved my problem:
#+call: ../test.org:hcw(d="foo")
Seems like rubber ducking kind of works ;).
Regards
hmw
Hello,
in a file named test.org I have an elisp src code block and a line like
this:
#+call: test.org:hcw(d="foo")
C-c C-c on that line executes the code block just fine. Copying the line
to another org file and pressing C-c C-c results in nothing obvious. On
the other hand, putting a code block
Hello,
Matthew Henderson writes:
> The following list:
>
> - label :: information
>
> when exported to latex generates:
>
> \begin{description}
> \item{label} information
> \end{description}
FWIW, here I get
\begin{description}
\item[{label}] information
\end{description}
Regards,
--
N
13 matches
Mail list logo
