You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really like that I can organize my workflow with sections and sub-sections and sub-sub-sections, but I'm wondering if there is a way to close a sub-section to return to the section. I was writing a scene the other day where a character goes into a flashback. In this case I had a section where the character is talking to someone and then a sub-section called "flashback" where they experience a memory, but then they come out of the memory and return to the conversation. So is there a way to close the sub-section and continue writing in the section?
The text was updated successfully, but these errors were encountered:
Hi! Sorry for the late reply - although I think I already answered on the discord?
just so that it's public here and for posterity, this isn't something which is currently covered by the fountain spec, probably because it's heavily inspired from markdown, and this isn't something which would really make sense in markdown. However, as you say, it would definitely be interesting to implement this in fountain. It could be as simple as something along the lines of
# Section
Some action
# ---
or
# Section
Some action
/#
I'm not sure which would make the most sense, or be least likely to cause conflicts or weird edge-cases?
I really like that I can organize my workflow with sections and sub-sections and sub-sub-sections, but I'm wondering if there is a way to close a sub-section to return to the section. I was writing a scene the other day where a character goes into a flashback. In this case I had a section where the character is talking to someone and then a sub-section called "flashback" where they experience a memory, but then they come out of the memory and return to the conversation. So is there a way to close the sub-section and continue writing in the section?
The text was updated successfully, but these errors were encountered: