> As for the problem with REST you raised, I am inclined to remove it from
> syntax doc for the time being - it only creates more confusion,
> unfortunately.
Makes sense, thanks. Is there anything we do to mark patches as rejected? I
removed [PATCH] from the subject line.
--
Tom Alexander
pgp:
Thank you! Makes sense.
--
Tom Alexander
pgp: https://fizz.buzz/pgp.asc
in html gmail, i can capture message body text and whatever else.
gmail has an html version and a js version. html is faster and better for me.
in disroot.org, if i try to capture message body text, it seems to
capture just the link but does not capture the message body text.
--
The Kafka
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> It seems, I was not the only person who had an impression that `woman'
> is
Juan Manuel Macías writes:
> Ihor Radchenko writes:
>
>>> In tables there is more consistency because :float is a float
>>> environment (table or any arbitrary value) and :environment is a table
>>> environment (tabular or any arbitrary value). Here :placement :options
>>> and :align act as what
Ihor Radchenko writes:
>> In tables there is more consistency because :float is a float
>> environment (table or any arbitrary value) and :environment is a table
>> environment (tabular or any arbitrary value). Here :placement :options
>> and :align act as what is expected of them:
>>
>>
Juan Manuel Macías writes:
> Ihor Radchenko writes:
>
>> Further, we also provide :environment and :options attributes that do
>> the same thing, but without special treatment of standard
>> t/multicolumn/wrap/sideways/nil values in :float.
>
> t/multicolumn/wrap/sideways/nil... and any
Exporting HTML file from Org-mode, f.i. with `org-html-export-to-html',
I expect to get a newline after the closing tag, but it's not
added. I believe this used to work with previous versions of Org-mode.
Am I missing something?
Thanks.
Emacs : GNU Emacs 29.1 (build 2,
Johannes Keller writes:
> Error message when adding an item to a bullet list [9.6.6 (release_9.6.6 @
> /usr/share/emacs/29.1/lisp/org/)]
Thanks for reporting, but may you please share the error message you are seeing?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org
Hi
Starting with this
#+begin_src
| pos | rango | weight |
|-+---+|
| 23 | 329 |307 |
| 71 | 329 |259 |
| 77 | 333 |257 |
| 58 | 333 |276 |
| 155 | 310 |156 |
| 164 | 325 |162 |
| 203 | 330 |128 |
#+TBLFM: $3=($2+1)-$1
#+end_src
Ihor Radchenko writes:
>> For context, I use '#+OPTIONS: num:nil', which means that '[[link]]'
>> exports as 'link' and not a section number.
>
> I am confused. num:nil just means that section titles will not be
> numbered. It has nothing to do with links, AFAIK.
My sentence says it all, but if
Hi, this is a proof of concept of how a sort of 'templates with
arguments' can be used within Org, just with Org’s own resources at the
user level. It occurred to me that org src blocks might be handy for
this. For this test I just made a disguised format string using this
function:
┌
│
Visuwesh writes:
> Attached patch adds yank-media and DND handler to attach files in the
> clipboard and dropped onto an Emacs frame respectively.
>
> The yank-media handler for images is well tested, I use it frequently
> however, rest of the stuff aren't really tested since I don't use a GUI
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
14 matches
Mail list logo