Hi Christian,
thanks for the hint!
I can confirm that the warning gets obsolete, when I enter a blank line
between the keywords.
This is the actual item, which is annotated with keywords:
#+DOWNLOADED: screenshot @ 2026-05-15 13:25:28
#+attr_org: :width 400px
[[attachment:2026-05-15_13-25-28_screenshot.png]]
It would feel normal to me to have these three associated items
consecutively aligned. Or optionally(!), if someone prefers, have it
with a separating blank line. Hence, I'd assume both should be possible.
Therefore I am still somewhat puzzled, also because this seems to be
like a new markdown syntax rule for me.
For clarification I'd also like to add that the above entry was
auto-generated by function org-download-clipboard (from org-download
package).
Would you point towards org-download, namely using outdated syntax rules
for the generated attachment text or can you agree with my personal
flavour, i.e. having these three lines associated with the actual
downloaded attachment, treated somehow like a proper block (with no
separating blank lines)?
Thanks again,
Daniel
Am 20.05.26 um 11:36 schrieb Christian Moe:
tocoda <[email protected]> writes:
Hello,
I still encounter lint errors for my attachments, e.g.
38 low Independent keyword DOWNLOADED may be confused with
affiliated keywords below
Hi, Daniel,
This means a keyword is not separated with a blank line from an
"affiliated" keyword below, i.e. one that applies to a following
element. E.g.
#+PROPERTY: key val
#+NAME: tbl1
| A | B |
triggers the warning,
#+PROPERTY: key val
#+NAME: tbl1
| A | B |
does not.
So you can look for a `DOWNLOADED' keyword to see if this is what is
happening and where it comes from; I don't think there's any such
keyword in Org by default.
Regards,
Christian
