"Christopher M. Miles" writes:
> [[PGP Signed Part:Undecided]]
> There is attributes setting above image link to specify image inline preview
> size. Like this:
>
> #+begin_src org
> ,#+ATTR_ORG: :width 500
> ,#+ATTR_LATEX: :width 5.0in
> ,#+ATTR_HTML: :width 500px
>
"Christopher M. Miles" writes:
> [[PGP Signed Part:Undecided]]
> There is attributes setting above image link to specify image inline preview
> size. Like this:
>
> #+begin_src org
> ,#+ATTR_ORG: :width 500
> ,#+ATTR_LATEX: :width 5.0in
> ,#+ATTR_HTML: :width 500px
>
> On Sep 10, 2022, at 12:03 PM, Colin Baxter wrote:
>
>
> I seem to remember that the option
>
> #+ATTR_ORG: :width 100
>
> could scale the display of an image in an org-mode file. This no longer
> works - perhaps it never did. How should I scale an image display in an
> org-mode file (not
Max Nikulin writes:
> On 06/09/2022 21:34, Max Nikulin wrote:
>> Does anyone have an idea why it was necessary to drop completion of stored
>> links based
>> on their description for the sake of ido?
>
> I have no idea what is the proper way to enable ido for `org-insert-link'.
> Functions
Maybe there are other options, but I think the canonical way is to use the
variable `org-image-actual-width’. The help mentions some ATTR_XXX options, so
you may find more answers there!
Dominik
Colin Baxter writes:
> I seem to remember that the option
>
> #+ATTR_ORG: :width 100
>
> could
I seem to remember that the option
#+ATTR_ORG: :width 100
could scale the display of an image in an org-mode file. This no longer
works - perhaps it never did. How should I scale an image display in an
org-mode file (not exported)?
Best wishes,
Colin Baxter.
On 10/09/2022 15:54, Ihor Radchenko wrote:
Guillaume MULLER writes:
My (unsuccessful) approaches so far to find a solution:
1. remove the automatic \begin{center} inserted by #+INCLUDE
=> using :center nil in #+INCLUDE or in additional #+ATTR_LATEX added above
#+INCLUDE does not work
2.
On 06/09/2022 21:34, Max Nikulin wrote:
Does anyone have an idea why it was necessary to drop completion of
stored links based on their description for the sake of ido?
I have no idea what is the proper way to enable ido for
`org-insert-link'. Functions and variables specific to ido were
Guillaume MULLER writes:
> My (unsuccessful) approaches so far to find a solution:
> 1. remove the automatic \begin{center} inserted by #+INCLUDE
>=> using :center nil in #+INCLUDE or in additional #+ATTR_LATEX added
> above #+INCLUDE does not work
> 2. remove the use of \scalebox by using
I'd like to show some use cases as examples of long lists that I do not
consider micromanagement.
I started managing tasks with pen and paper, then Palm, Remember the Milk, and
others. None of them worked fine. I reached Org-mode because I have read about
it and it was in my try-list. It has not
Felix Dorner writes:
> I have a silenced codeblock, that I postprocess to push the result (a
> password) onto the kill-ring, and then returns "Password copied" (showing
> in the status line). This works very nicely. I'm now looking for the cherry
> on the cake: I'd like to render the #+CALL as a
Perry Smith writes:
> The manual says I can type #+ and then hit M-tab to get the list of
> completions. In my case, flyspell-mode had stolen that key binding so I
> disabled flyspell-mode.
>
> There are 100 #+ candidates. Is there a nice place that lists them and
> documents each one? So
Sébastien Rey-Coyrehourcq
writes:
> Moving from org-contrib to https://repo.or.cz/org-contacts.git ,
> accessible with melpa, the documentation is mostly into the source-code
> actually, i found few example on the web .
>
> What property field are correct :MOBILE:, :PHONE:, :BIRTHDAY: , and ?
"Rohit Patnaik" writes:
>> Recentering is purely a visual thing. It should be safe to add.
>
> I've added the recentering behavior in the attached patch. The recentering
> part
> was more important for me than the point jumping to the heading, because
> sometimes the match would appear at the
14 matches
Mail list logo
