On 2023-04-14, at 22:39, No Wayman wrote:
> https://www.github.com/progfolio/doct may be helpful here
Ha, interesting! Though I'm not sure how useful this is (at least for
me) - after all, I write capture templates once per year (or more
seldom), and I just copy-paste from my other templates
Here's a small enhancement I wrote to add customizable variables for the
`org-export-dispatch' UI options that don't already have one. I almost always
export with "Body only" switched on, and I got tired of manually toggling it
each time; while I was at it I also added variables for "Visible
On 15/04/2023 08:36, Samuel Wales wrote:
but now the problem is htat this essential ff extension is completely
broen for me. i upgraded firefox, and now it is popping up a window
asking [unselectable text paraphrasing] whether i want emacsclient
oprning protocol iink.
i affirm but no capture
Ihor Radchenko writes:
> The question is: does iCalendar allow something like
>
> DTSTART;TZID=America/New_York:19970105T083000
> RRULE:FREQ=YEARLY
> DUE;TZID=America/New_York:20070105T083000
>
> and repeats past DUE?
>
> If not, we have to choose when exporting from Org source - either to
>
i am very sorry, i got myself in over my head. i do not undestrand
what you are suggesting. if a change on the ff side i cannot do it,
bu perhaps you are suggesting making emac pop up an x seector that
chooses the filing option.
for yers i have used an unsophisticated heursitic in the template
On Thu, 13 Apr 2023 at 12:47, Ihor Radchenko wrote:
> I suspect that it might be Emacs problem.
Ok, you win, done: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62847
Best,
Gustavo.
https://www.github.com/progfolio/doct may be helpful here
Jack Kamm writes:
> Ihor Radchenko writes:
>
>> Another scenario we may need to consider is when schedule has a repeater
>> while deadline does not, and vice versa. The former scenario is probably
>> valid - a VTODO with limited number of occurrences.
>
> That is an interesting idea; and we can
Ihor Radchenko writes:
> Another scenario we may need to consider is when schedule has a repeater
> while deadline does not, and vice versa. The former scenario is probably
> valid - a VTODO with limited number of occurrences.
That is an interesting idea; and we can use the UNTIL or COUNT
writes:
>> > There is a related issue about EOLs, not just \r\n -- each line should
>> > be a maximum of 75 characters; this is handled by
>> > org-icalendar-fold-string
>>
>> May you please provide a link to the iCalendar spec document section
>> describing this requirement?
>
> It's in
You're probably using the CSL export processor then.
On Fri, Apr 14, 2023, 9:47 AM Durham Smith wrote:
> When inserting a link a reference using org-cite (e.g
> `[cite:@name_of_ref_in_bib_file]`) and generating the latex instead of
> generating code like `\cite{name_of_ref_in_bib_file}` what
Durham Smith writes:
> When inserting a link a reference using org-cite (e.g
> `[cite:@name_of_ref_in_bib_file]`) and generating the latex instead of
> generating code like `\cite{name_of_ref_in_bib_file}` what get in the
> generated .tex file is the actual citation written out in full. Is there
When inserting a link a reference using org-cite (e.g
`[cite:@name_of_ref_in_bib_file]`) and generating the latex instead of
generating code like `\cite{name_of_ref_in_bib_file}` what get in the
generated .tex file is the actual citation written out in full. Is there
any way to change this
I am looking for exactly the feature in
https://lists.gnu.org/r/emacs-orgmode/2019-01/msg00203.html:
I have a note with many links, but would like to export that note as landing
page as text stripped of links.
Has there been any progress in the last 4 years on this,
or any hint on how to get
Andreas Gerler writes:
> * lisp/ob-eval.el: (org-babel-eval-error-notify): Display standard
> error only if command exits non zero.
>
> The problem is that sql connections might give warnings.
> Now the information is available in the *Org-Babel Error* buffer
> without displaying.
> If you need
> Uwe Brauer writes:
> This one is tricky.
> Table export is intentionally decoupled from general export settings:
I see, that explains it.
[Snip]…
> I understand that the suggested `org-export-region-as' will not work
> because we don't have ox-csv. And changing the way table export
Uwe Brauer writes:
> I asked a similar question three years ago, the first two columns are
> not exported because of this
>
> (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
Ihor Radchenko writes:
> I am attaching tentative patch that simply keeps spaces, but if and only
> if the previous object does not end with whitespace (including newline).
Applied, onto main.
Fixed.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=960722661
--
Ihor Radchenko
On Fri, Apr 14, 2023 at 10:13:48AM +, Ihor Radchenko wrote:
> "Stephen J. Eglen" writes:
>
> >> https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab5787942271a546b51891996
> >
> > Thanks for copying me in on this.
> >
> > There is a related issue about EOLs, not just \r\n
"Stephen J. Eglen" writes:
>> https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab5787942271a546b51891996
>
> Thanks for copying me in on this.
>
> There is a related issue about EOLs, not just \r\n -- each line should
> be a maximum of 75 characters; this is handled by
>
Ihor Radchenko writes:
> Ruijie Yu via "General discussions about Org-mode."
> writes:
>
>> Major mode was erronously set to shell-script-mode because of the empty line.
>
> There is no error there. The line in question is inline stdin redirect
> in shell. "#..." is what is fed to exec emacs.
Ruijie Yu writes:
>> You can do either way, depending on which part of the script you want to
>> edit.
>
> I tried to actually compare the two versions, and found out that the
> lexical-binding does nothing at all during the script execution,
> regardless of whether there is an empty line or
Nathaniel Nicandro writes:
>> Ideally, fontifying ANSI sequences should be fully controlled by users:
>> 1. We may not want to touch src blocks by default, when
>>`org-src-fontify-natively' is set to t. Only, maybe, provide an
>>option. Or you may better publish a minor mode that does
Ihor Radchenko writes:
> Ruijie Yu via "General discussions about Org-mode."
> writes:
>
>> What is the expected major mode for orgweb/publish.sh? When I open it,
>> I see it is in `shell-script-mode'. This is what I see in
>> orgweb/publish.sh:
>>
>> --8<---cut
Ruijie Yu via "General discussions about Org-mode."
writes:
> Major mode was erronously set to shell-script-mode because of the empty line.
There is no error there. The line in question is inline stdin redirect
in shell. "#..." is what is fed to exec emacs. There is no intention to
define mode
Ruijie Yu via "General discussions about Org-mode."
writes:
> What is the expected major mode for orgweb/publish.sh? When I open it,
> I see it is in `shell-script-mode'. This is what I see in
> orgweb/publish.sh:
>
> --8<---cut here---start->8---
>
Ruijie Yu writes:
>> Hello,
>>
>> What is the expected major mode for orgweb/publish.sh? When I open it,
>> I see it is in `shell-script-mode'. This is what I see in
>> orgweb/publish.sh:
>>
>> --8<---cut here---start->8---
>> #!/usr/bin/env sh
>>
>> ":" ;
Ruijie Yu via "General discussions about Org-mode."
writes:
> Hello,
>
> What is the expected major mode for orgweb/publish.sh? When I open it,
> I see it is in `shell-script-mode'. This is what I see in
> orgweb/publish.sh:
>
> --8<---cut
Hello,
What is the expected major mode for orgweb/publish.sh? When I open it,
I see it is in `shell-script-mode'. This is what I see in
orgweb/publish.sh:
--8<---cut here---start->8---
#!/usr/bin/env sh
":" ; exec emacs --quick --script "$0" -- "$@" # -*-
29 matches
Mail list logo
