emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Asilata Bapat <asilata@gmail.com>
Cc: emacs-orgmode@gnu.org, Timothy <tecosaur@gmail.com>
Subject: Re: [BUG] org-agenda-skip fails in batch mode because comment-start-skip is nil
Date: Thu, 23 Jun 2022 21:13:56 +0800	[thread overview]
Message-ID: <87h74ba5ez.fsf@localhost> (raw)
In-Reply-To: <87pmj2hj51.fsf@gmail.com>

Asilata Bapat <asilata@gmail.com> writes:

> Ihor Radchenko <yantar92@gmail.com> writes:
>> Could you please provide a detailed reproducer?
> Sure. I have attached the files "mwe-data.org" and "mwe-export.org".
> To reproduce, save both files in the same directory. Then open mwe-export.org, navigate to the "Export script" heading, and evaluate (Ctrl-C Ctrl-C) the shell source block.


The offending commit is ec6d1df9bc.
The author of the commit claims that we never ever need to activate
major mode inside export:


>> > I'm still unsure the patch is correct: what if people *need* major
>> > mode initialization before any contents is exported to a file?
>> I haven't responded to this concern, because I haven't been able to
>> conceive of a single situation where loading the normal-mode for the
>> exported file could be desirable.

So, we do have the situations where initialization of major mode is
required during export.

Timothy, do you have any comments?
I am inclined to revert ec6d1df9bc.


  reply	other threads:[~2022-06-23 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 17:44 [BUG] org-agenda-skip fails in batch mode because comment-start-skip is nil Asilata Bapat
2022-06-19  1:47 ` Ihor Radchenko
2022-06-21  1:42   ` Asilata Bapat
2022-06-23 13:13     ` Ihor Radchenko [this message]
2022-09-28  4:35       ` Ihor Radchenko
2022-09-28  4:41         ` Asilata Bapat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h74ba5ez.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=asilata@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).