ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

Main Area and Open Discussion > General Software Discussion

I'm thinking of going primitive, with discursion into zettelkasten

<< < (227/233) > >>

Paragraphs, Lines and Enter
This remains an issue. If someone writes paragraphs only (ie no single new lines within the paragraph), then there may be no effective difference between a line and a paragraph - everything will depend on the settings of the export/conversion process. Depending partly on the use of copy/paste and the settings used within that.
-Dormouse (May 09, 2022, 09:15 PM)
--- End quote ---
Given the lack of a reasonable combine and export option in Obsidian, I decided to do a little testing. Two md files, one with an empty line between the lines (ie markdown definition of a paragraph) and one without (ie lines only), exported into docx

Inspire Writer - exported the no empty line file "correctly" (from my usage point of view) into paragraphs, and the one with markdown paragraphs into paragraphs with an empty space between the paragraphs.
iA Writer - exported the empty line into paragraphs, and the no empty line file was concatenated into a single paragraph.
Typora was the same as iA Writer. As was Writage.

In other words, Inspire Writer interprets markdown lines as if they were paragraphs - which is the way many people intend. But iA Writer and Typora stick rigidly to the markdown standard paragraphs. I was a little surprised by Typora because when I enter directly into it, the Enter = New Paragraph, but quite reasonably it regards that just as a keyboard adjustment for WYSIWYG.

Which means, for me, that I'd have to add an extra process (double spacing lines in text editor) if I wanted genuine paragraphs without adjusting keyboard behaviour to double Enter every time I pressed Enter should I type in Obsidian or iA Writer and export through iA Writer, Writage or Typora. Writing in Typora always exports as I want, as does writing in Inspire Writer. And writing directly into docx obviously works perfectly.

The combining options in Inspire Writer work well; in iA Writer the embed system export requires combining files one at a time - functional but quite high friction if done often, and no preview.

Given the lack of a reasonable combine and export option in Obsidian
-Dormouse (May 12, 2022, 06:09 PM)
--- End quote ---
While I was looking at it, I thought I ought to work out what I think is currently the best workflow for longform writing in Obsidian. The lack of tools for a single file approach makes it hard to recommend that purely. So, ..

A separate vault (or folder) for the long project.

Plugins required:

* Bartender (for manual sequencing of files in the file explorer)
* Pandoc (possibly + Obsidian Enhancing Export)
* Novel word count (for visible word or page counts for each file or folder)
* Better word count or File info panel (for word counts including a count for selected text, in the current note; and other info in the FIP)
* Note Refactor - (optional - to make files easier to split)
* Hover Editor (to give the option to do all the editing via the large document rather than the separate notes)
The basic technique is to have a single note that contains all the scenes, chapters etc as embeds, and then to export that document into the desired format.

Workflow(s) - there's a number of options.
One would be to write from the beginning using the large note with embeds and headings. I feel it is likely to be better to only do that at a later stage.
Easier to start in the conventional Scrivener/Ulysses way with separate scene/chapter notes in the explorer. With bartender, and using folders, it's easy to see everything in sequence and with their word count (via Novel Word Count). Once you are ready, you can select all the required notes and paste into a new note as links, and then make those links embeds. The bartender sequence will not be preserved, but, if the embeds are made into headings, the outline will allow them to be moved around.

Export is straightforward, but attention needs to be paid to the line/paragraph distinction.

Also notice Tangent Notes. Very early stages.
-Dormouse (February 19, 2022, 07:08 AM)
--- End quote ---
Just updated it. Does feel interesting. Very visual, card style interface. I could imagine working in it. Especially if I wrote many short pieces or short notes.

Tangent is awesome. My flirting with logseq and neovide didn't go well. I wasted a lot of time. This is such a crucial app to get right that sometimes I spend too much time searching. But I'm happy I found Tangent. This forum delivers!

Tangent is awesome
-urlwolf (May 14, 2022, 12:14 PM)
--- End quote ---
Once you have spent enough time with it, I'd be interested in your ideas of its strengths and weaknesses.
It feels too early in its development for me to use it (and my current use cases don't seem ideally suited ot it), but I have liked the look and feel when I've looked it over.


[0] Message Index

[#] Next page

[*] Previous page

Go to full version