From: Christian Moe <mail@christianmoe.com>
To: emacs-orgmode@gnu.org
Cc: Fionn Stephens <fionnstephens@protonmail.com>
Subject: Re: [FR] Please add support for screenplay formatting
Date: Mon, 03 Jul 2023 16:32:55 +0200 [thread overview]
Message-ID: <87o7ktkqug.fsf@christianmoe.com> (raw)
In-Reply-To: <87a5wdgn3p.fsf@localhost>
Ihor Radchenko writes:
> Fionn Stephens <fionnstephens@protonmail.com> writes:
>
>> I think support for screenplay formatting would be a useful feature to add. Like to how comments or quotes are done, it could be in between the tags: #+BEGIN_SCREENPLAY and #+END_SCREENPLAY. I think using the markdown used by Fountain would make the most sense.
>>
>> For example, a section could look like:
>>
>> #+BEGIN_SCREENPLAY
>> INT./EXT. BLOOM HOUSE - (PRESENT) DAY
>> ...
>
> May you please elaborate? What is screenplay? Is it a markup format?
> What do you mean by support? Export? Font-lock? Something else?
Fountain is a Markdown-inspired plain text format for screenplays
(https://fountain.io/).
There exists a fountain-mode major mode for Emacs.
To my mind, Org should not support every kind of markup/markdown format
there is, but to the extent Fountain is the best format for screenplays,
and Org is good for organizing bits of screenplays, I think maybe using
Org-babel src blocks is the way to go?
Even without a dedicated ob-fountain package to support it, it can be
used today for tangling screenplays from blocks of Fountain format with
noweb syntax, editing blocks in fountain-mode, some limited syntax
highlighting etc.
Yours,
Christian
next prev parent reply other threads:[~2023-07-03 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 13:00 [FR] Please add support for screenplay formatting Fionn Stephens
2023-07-03 13:07 ` Ihor Radchenko
[not found] ` <TWArAUwC8kxJDdScIWQFyfTWlgAyg7RAhTzBQ7WNkDlaSVNJ1mk_5zKmLtX0tZiz7-nbaTesc7uAzsYUYoQhS6KQzoA5pzNHr6klZC6Qq0c=@protonmail.com>
2023-07-03 13:51 ` Ihor Radchenko
2023-07-03 14:33 ` Fionn Stephens
2023-07-03 16:02 ` Ihor Radchenko
2023-07-03 14:32 ` Christian Moe [this message]
2023-07-03 15:59 ` Ihor Radchenko
2023-07-03 13:53 ` Bruno Cardoso
2023-07-03 14:41 ` Fionn Stephens
2023-07-03 16:04 ` Ihor Radchenko
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87o7ktkqug.fsf@christianmoe.com \
--to=mail@christianmoe.com \
--cc=emacs-orgmode@gnu.org \
--cc=fionnstephens@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).