topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Saturday April 18, 2026, 9:56 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Recent Posts

Pages: prev1 2 3 4 5 [6] 7 8 9 10 11 ... 79next
126
But with current (low) prices for storage, why does it matter?
Doesn't matter much. I was looking for reasons not to put more emphasis on docx and expected file size to be much larger as it's one of the justifications for plaintext I've come across frequently in fora for markdown apps. I remembered it being bigger myself. Half expected docx to be MB with the plaintext just being a few kb.

Storage price may be down but bandwidth and transfer can be an issue. Used to be a huge one for me.

The other side of it is computing power. Which is an issue on mobile. Loads more stuff in docx files and compressing and opening adds more load.

My current plan is to save the updated file every day,  date stamp in file name, and keep them all indefinitely.  I have versions,  but see this as different. So all the files will add up in the end, even if the individual files are small. They will also be backed up locally and cloud.

127
It's not unfair from my point of view since the programs using the MD and txt files don't zip them when saving. And I'm not going to add an extra process to my workflow.

It came as a surprise to me since I'm used to seeing my word processor files as quite large.
128
I thought I ought to test size of the different formats, to see how much extra space docx would take.
Thought the simplest method was simply to use the exports from Inspire Writer. I sed a 21,500 word file.

Results:
docx      55kb
rtf        128kb
md       117kb
txt        231kb
More or less the reverse of expectation, but does show that the docx size burden is a non-issue for what I do.

The other observation is that Word understood the exported headings, but Atlantis didn't.
I saved the docx from Word and it moved up to 78kb; Saved it as docx from Atlantis and it remained at 55kb, saved it as RTF and it became 122kb.
I added a few headings in Atlantis, and Word understood those. So looks to be an issue in Atlantis understanding headings created in other programs.
I checked again by adding a couple of headings in Word itself. Atlantis recognised one but not the other.

I thought I'd test again by exporting from Typora. It produced an md file at 118kb, and a docx file at 58kb.
So similar results to Inspire Writer, and suggesting that IW wasn't simply doing peculiar things.

Only conclusion seems to be that docx actually produces smaller file sizes than md, at least for the type of files that I produce (simple text files, with virtually no formatting). The files took longer to generate, so maybe there's compression involved in producing the docx files. I've no idea. The results are completely the reverse of what I expected and I'm still not sure I believe them. Still, the results do suggest that I won't be losing disk spaace by workig with docx. I have no idea at all why txt was twice as big as the other plaintext formats.

Addendum: Atlantis devs wanted to look at docx files where it failed to recognise headins. I'd deleted them. I made some more test files and Atlantis worked flawlessly. I might dig back through versions, but I might also not spend the iime and wait until I encounter a problem in real life - it's the type of situation where I'd expect devs to come up with a quick fix. So I don't regard this as an issue any more.



129
Another revision after playing around more. I'm about to start a huge project, so I want the workflow to be as right as possible before I start because changing things around later might be time consuming.

Programs:
Inspire Writer - the nicest environment to write in from my personal point of view. But hit a clunk when I saw it didn't treat HTML comments as comments and just exported them into Word. Ulysses has similar issues apparently, and according to David Hewson also breaks front matter in external files. idk if IW does that, but it has made me wary about relying on it - there's already the issues with idiosyncratic markdown and useful features being in the database. I don't believe it plays as nicely with other programs as I need.
iA Writer - a nice enough writing environment, but it's pretty hardline and rigid. Works okay with other programs. No WYSIWYG mode. Available on all platforms.
Word - it's not a lightweight text entry program, but it is to my mind much more useable than it used to be for writing, and no need to look at previews to estimate how a document will look in Word. Definitely the one to use once I have finished first draft, and not impossible before that. And, of coure, I could use Wordpad as my lightweight data entry program, excepting the lack of dark mode :( . But then there are the other lighter word processors - and Atlantis does have many writer oriented features.
Pure Writer (Android) - this is my favourite writing program on Android. I may need to remember to change the default setting to txt instead of md.

One of the big issues with this project is that I want a clear idea of the whitespace on pages as I am writing, and markdown is particularly poor for this. Specifically I need to see paragraph indents as I write and this requires new lines being paragraphs.
I tried looking at other programs like Typora (probably not out of it, though it has no specifically useful features), and I know Typora can do this. But when I pasted example markdown text, it didn't pick up all the paragraphs that needed indenting. It did pick the missing ones  as lines, which is more that iA Writer did. Markdown quirks and incompatibilities are extraordinarily irritating. I don't know about it keeping things safe for the long-term, because it's not great at passing them from one program to another. For a project his size, I need everything to run predicably and reliably.

Database or files?
Strong preference for files. Willing to accept database for a given period. But not minded to trust IW's database for this project. I'm not familiar enough with it, I've seen a few glitches in its interactions with other programs and its Ulysses syntax is eccentric. Interoperability is not a strength of databases.

Markdown or Rich Text?
This wasn't a question until recently - it was markdown of course. But markdown's not very interoperable, as I'm finding. You can shift from one program to another simply enough - it's just a few changes, and all is done - but constant switching between one program and another is a very different beast. `I'd assumed that I would settle on one program to use, and I very nearly did - more than once, but always there were little glitches - like the paragraph indent of iAW appearing only in the preview pane (in Pure Writer, they appear in the edit pane, but not in the preview pane, which strikes me as the more correct behaviour; I don't need indents exported, other programs will have their own settings). Minor but it will always niggle.
I haven't decided, but I'm starting to veer towards rich text. I know that works.

One long file or many short?
I haven't decided this. It will depend on how well it works. OPML export from Workflowy isn't really a constraintas it can be exported  in chunks, and it is easy to combine or split files by heading.
I'll start long and go from there.
If I go initial markdown, then I'll use HTML comments to contain section information from Workflowy.

Reflection on journey, Obsidian and all.
In practice, even if I go to rich text for this project, that's not a change of direction. This is just for writing, which I've not been examining in detail. I'd hoped Obsidian would become a good program for writing, but it has gone in the other direction and is increasingly becoming a programmers' (and students) program. I don't trust IW sufficiently, and Ulysses is Mac only. All other markdown editors tick some boxes, but not enough, and while they will all work on the same file, they don't always agree on the syntax. I might still go that way but I'm starting to feel not. I'm likely to go txt and docx. Which is where I have before, from time to time.

For research now, notes etc, it is wikilinks all the way and I'm agnostic whether that's with Workflowy or Obsidian or another PKM app, Not many focus on files unfortunately, so I will have to make the best of what I can find. But the important thing is the files and the folder structure. Or so I tell myself.

And after all that humming and hawing, and playing with the programs again, I'm going to go with Inspire Writer for the writing. The reason is simply that I know I will write more words using it than any alternative. And get them in the right order easier. I'll mitigate the risks of the database (I will use the database rather than external files) with daily exports to md and docx. It's an odd thing, I sit down with it and want to write; I sit down with the others and there are endless temptations to fiddle with the program.

Update - Now feels even odder. I've set Atlantis up to imitate, as best I can, the display settings in IW, using the same font/spacing etc. But it is still not quite the same. Feels heavier and not as easy to read. Nevertheless I've managed to get Atlantis into contender territory.And I'd forgotten Atlantis' blazing speed; other programs struggle to match it, depite being plaintext only: Atlantis is faster loading and working with the docx version of a document than they are with the markdown version. (tested with War and Peace)..
130
First draft writing in IW and/or iAW.
Since it imports and exports OPML natively, I thou8ght I ought to have another look at Scrivener.
Was going well, apart from the complexity (manageable because I know it), and then it crashed the PC. It crashes very, very rarely, so I won't even look at it again for a while.

One thing I noticed when I was comparing the same text, pasted in, was how different they all looked. And my preferences weren't 100% consistent.
131
felt clunky - particularly the shift from the outline to the writing
obvious to put the section details into YAML format in Workflowy bullets
Possibly not clunky, but unnecessary friction. So I've given that up. I did try alternative approaches but they clunked too.
And, anyway, it's as easy to use the information in native Workflowy as it is to use in a YAML or other adjunct of the writing file.

So now that's what I'll do. Creating, devising, planning, organising in mindmap, kanban and outline. (In the main that's just a single OPML mediated export from Mindomo to workflowy.)
First draft writing in IW and/or iAW.
Then editing, rewriting & the multiple & etcs in Word.

I'm trying to get this right because I'm just starting a huge project, and messing about in the future will be time consuming.

My personal view is that Word has progressed right down the food chain. I don't like it for first draft writing yet, but it wouldn't take much for that to happen. Markdown syntax is a pita and can only do what I want by adding HTML.

Many programs that claim to use Markdown are actually databases. Roam, Amplenote, Trello, Logseq etc
Obsidian is fundamentally files, but supplemented by many small databases.
docx is just a database in a file

This post is interesting describing abandoning the PKM tools he had presumably been very keen on at one point.

I used to think that once I have collected and organized these great ideas, I will be better thinker and produce better results.
I was wrong.
...
notes are useless after some time. I either forget about them, or I don’t know why I wrote them in the first place.
I find most of the notes I wrote a few years ago pretty useless for the current me
the idea that notes are used to store information (knowledge) for a long term is misguided. There is no permanent storing or organizing of knowledge. Knowledge is highly transient stuff.
I need to think of myself as writer than a knowledge worker


I've never been in the same position he was in as far as collecting thousands of notes is concnerned. I have fewer; they all had, and retain, a potential use; and I'm well aware that stuff I have apparently abandoned can suddenly return as active work - but the reversion to rich text is.

132
General Software Discussion / Re: Contra Chrome
« Last post by Dormouse on April 17, 2022, 04:37 PM »
Most of the described issues apply only to Chrome - not Chromium. No shortage of good, privacy oriented Chromium browsers. Firefox not essential unles you want it.
133
appearance is very similar to Inspire Writer, though not quite as good
I've learned that one of the attractions of IW's appearance was its use of the often denigrated Droid Sans Mono font. I find it very easy to read. Suits my eyes. So I have switched to using it in many programs now, when I have the option to set a font.
134
A stray thought that occurred to me is that I'm surprised that no writing program has tried to use the same trick as Obsidian by defining all the contents of a folder as a project/document. It could keep a small database about the project in the folder and have a separate folder elsewhere which contains information from all projects. This would make it easy to calculate words per day etc across all projects, sequence fo files in a project etc etc. And no need for the program to be designed as a database hidden from other programs.
135
My planned workflows atm:-

1. Mindomo > Workflowy > Inspire Writer > Word
2. Inspire Writer > Workflowy > Inspire Writer
3. Inspire Writer > Word > Inspire Writer

The plan was to make Workflowy central, but it has always felt clunky - particularly the shift from the outline to the writing. I tested writing in Workflowy, but it's not designed for it and never felt smooth. The big question was what exactly ought to be done in Workflowy and how would it be transmitted to the writing program.

I decided to try iA Writer. I'd had it a while but never seen that it was worth using. Maybe my revisit was triggered by reading multiple Ulysses Vs iA Writer reviews (usually won by Ulysses). The big selling point for iA Writer was that the Windows version was very functional, it has Android and iOS apps, as well as Mac, and it is a purpose designed writing program that has been going for nearly twenty years. And indeed it works okay, and appearance is very similar to Inspire Writer, though not quite as good to my mind. And it is pure local file rather than a database, so interoperability with other programs should be straightforward; it hides hashtags in output (v.good!). And, being a standrd markdown editor (multimarkdown), it works with YAML, which Inspire Writer doesn't.

Which makes it obvious to put the section details into YAML format in Workflowy bullets notes, and thence, via OPML, into markdown notes. The YAML approach requires using individual notes rather than a single long document since front matter has to be at the front. But splitting at headings is easy enough. The iA Writer method to combine segments into a document is simply to drag the files into a document file. Preview is a check to see that it is combining as wanted. And iA Writer works as cosily with Word as Inspire Writer, which ticks my other essential box. A secondary benefit is that the files are always available to any other markdown editor I might choose to use, including Inspire Writer.
136
Visual Studio Code
Electron?
Forgot: it cannot be electron-based.
137
General Software Discussion / Re: WinPatrol appears dead
« Last post by Dormouse on April 03, 2022, 03:43 PM »
WinPatrol was nice and simple, unless you chose for it not to be.

One lesson I took from it is that handing on such a project frequently fails however carefully it's done. I've seen quite a few instances of that. Also true for large company taking over a small; rarely ends with the product developing as it would have done if the original developers had the resources of the larger one. Even when the original developers stay on. As with WinAmp.
138
an editor that keeps versioning per sentence? That is, you can go to old versions of every sentence.
I think roam has that, but I dislike roam
So basically  an editor that saves in blocks and keeps versions of each block? (Assuming sentence effectively = block.)

It's not something I've ever looked for, so I don't know. but I assume it would have to be an editor with a database.
I'm afraid nothing immediately springs to my mind as likely. Apart, as you say from Roam. And presumably Roam clones either have it or aspire to it, since blocks are a key feature.
139
The admonitions/callouts are simple to write and potentially useful.
Because they are customisable, and foldable, and very popular, I thought I'd have a little play with this as a possibly useful way of adding notes and comments to documents. Certainly I can see many ways in which I could use them.
And customise for my particular purposes at the time - whether that be research or editing.

Then I thought there's other ways of achieving those effects more easily.
1. General comments can be done simply as a wikilink to another file  - the hover will have the comment.
2. Particular comments in families can be done as headings. Use an emoji for the heading and that's all that shows on the page when it's folded. Faster and more flexible. And the size of the emoji can be set with this syntax <span style="font-size: 250%;">emoji<span>
And, if there's a need to have the foldable comment in a quote block, that just takes one > on the next foldable line anyway.
And very fast to do with a text expander.

That actually suits me much better.
2022-03-17_00-29-29.png
Instead of
2022-03-17_00-31-17.png

Another advantage of this system is that it works in Word and Workflowy via OPML.

140
Came across novelWriter in my peregrinations. Also on GitHub
Looks promising but not ready for prime time yet (the only Export I could find was 'bulld novel project' on the tools menu). Though I've only had a quick look.

What I found interesting were the issues he's grappling with. Markdown compatibility vs usability; markdown Vs rich text; database Vs files.
I'm not sure if the program is built around a database - he's contemplating json for the next version - but the text files themselves seem to be hidden to avoid users editing them externally, potentially mucking up project data.
Since my markdown format allows for comments and commands, that regular markdown does not, I'm not sure how to preserve this in case of an export/import of the same project.
Other than that, it seems to utilise a standard two-pane markdown editor.
Decent focus and full screen modes + typewriter scrolling. Good stats.

otoh, some of the syntax choices strike me as odd. **=bold; _=underline. This is an awkward subset of the markdown spec. Most apps using **bold will use *italic which is easier to use and remember. There's an unnumbered heading level - not a bad idea in itself, but ##! Is pretty idiosyncratic. I'm not sure that all these choices have been deeply thought through.

I do think the future for programs like these is a hybrid database/files design. Obsidian started by selling itself as local files only, which is still true - but only up to the point where it also keeps databases including data on the files - and not just metadata.
141
I very much agree with the sentiment behind a recent comment on a a post on the Workflowy Blog

I would always vote for full LaTeX, markdown is very simple, but of course very limited ...
the majority do prefer clean simple formatting and WYSIWYG. Also, most people, including myself, abandon software even if it is functional, when it is not pleasing the eyes, you must "like" to work with it, otherwise you will not be productive.

So while I always like more formatting options ..., I am more inclined towards the concepts of block editors (like Notion, Nimbus, Craft ... and all the clones)

In the end, if you need to be productive, comfort and workflow is everything.

Also made me reflect on why markdown is a very poor match for me.
  • For the vast majority of the time I use no formatting or markup at all. Just paragraph and line breaks.
  • Since moving back to working in single large documents, I use headings - but once I pass h3 I find counting #s irritating; even html is better.
  • For the final document, I need underline and italics, rarely bold.
  • When reviewing, I also need colour (text and highlight) and strikethrough.
  • When publishing, I often need to control pagination.
Markdown doesn't tick these boxes at all. (It is compatible with but unnecessary for the first.)
Simple tables are possible, but it's not very good at them.

So we have variants. And most markdown editors go further adding extensions and scattering html in the file (underline being the most common). So if markdown is a bad fit, why not the more widely understood docx (which for me was always a txt/docx combo)

The most recent version of Obsidian (0.14 insiders only atm) effectively sherlocks the admonitions plugin. The admonitions/callouts are simple to write and potentially useful. They're not exactly incompatible with other markdown editors, but they don't work in them either.
142
I don't know if you can collapse a group of linked notes into a single document.
You can, but it's convoluted at best, and all options on a menu don't do the same thing. I wouldn't regard it as practical. Unless there's something about it I haven't discovered.

Works well if you want an HTML file.
143
Mini-Reviews by Members / Re: Inspire Writer
« Last post by Dormouse on March 09, 2022, 09:55 AM »
Ghostwriter ... FocusWriter ... OmniaWrite

Hi n8wachT,
Can you say more about why you would suggest these as alternatives?
I see very little parity in workflows or features.

I like FocusWriter, but, apart from minimalism, it has very little in common with IW. No autosave, isn't a markdown editor, formatting only comes through in odt/docx/rtf..

I didn't know Ghostwriter, but it looks like a traditional markdown editor with a few writer statistics. And the install options (Windows portable only, Mac has to be built from source) just scream high friction and Linux based.

I only had a quick look at OmniaWrite. Initial warning that latest update solved some security issues was hardly inviting. Rigidly based on books, Chapters, Scenes. Seemed very limited from what I saw.

IW is polished and functional for both long and short-form writing. Ulysses might deserve the design credits, but IW is still polished. (I look at some of the recent 'imporvements' in Ulysses and can't help wondering whether they're reducing its polish.)

I've noticed that Ia Writer has a new outline function (Windows only - hasn't arrived for Mac yet). Big step for Ia but it's still navigation only - no manipulation - so doesn't really make it much more suitable for long-form.
144
I'm okay with a very long document in a plaintext format, but I'd worry about a huge tome entirely in Word.
Doesn't seem like a problem. Tested it with War and Peace. No complex formatting etc, but it was only just over 2MB and pretty snappy. Perfectly manageable. Broke it once ("not responding"), but I was trying.

Briefly tested setting Word up for writing since it is so so long since I've used it like that, and it's not so bad. Had to change (set up) a few shortcuts - but I'm not big on shortcuts most of the time, so minor for me. Outlining flexibility - shifting lines, paragraphs etc - better than most programs (actually as good as any), which is very different to what I remember.  Word/paragraph/page counts good - though I don't think there's a session counter. Entirely practical tbh. Extremely configurable in some ways, and not at all in others.

Okay, it won't compete with WikidPad for Sanderson's Story Bible; or with the wiki-linking PKM apps for research and linking (I don't see how Sanderson's setup could be as good as one with incorporated wiki-links). Doesn't compete with Inspire Writer/Ulysses/Scrivener for writing in multiple projects. Don't believe there's a typewriter mode. But still much better than I had expected. And everything co-operates with it.
145
I need smooth workflows
IW ... is limited and rigidly not configurable. But everything is part of the whole and seems, so far, to be very reliable.

so when I found this quote
I also like how picky the developers of both apps are. Neither of them just add every requested feature. It needs to fit tightly into their app’s workflow.
In a Review comparing Ulysses with Bear I thought "Exactly!"
There are times when I'm happy to play and learn, but others when I need to get things done. Most writing is getting things done. Research too, but not quite such a high proportion of the time.

The problem with smooth workflow apps is that they are very very good if they match your workflow, but can be close to useless if they don't. But most of the newer PKM apps I've tried are in the very rough category (I'll except Amplenote, which simply didn't meet my needs). Obsidian used to be far smoother than most, but hasn't been the same since the move to CodeMirror 6 and Live Preview and the plugin explosion.

Also
The resurgence of Workflowy development seems to be associated with an increase in the number of developers from 2 to 14. Some in Ukraine.

And Also
Brandon Sanderson apparently does his outlining (he's a heavy outliner) AND writing entirely in Word. Maybe in a single long document?Story Bible in WikidPad. I'm okay with a very long document in a plaintext format, but I'd worry about a huge tome entirely in Word. Though I assume he has much more powerful computers that I have.


146
When I found IW, I was really just looking for a better writing front end to cover me for markdown and rich text workflows. Turns out that it will be used further into the backend too.

My planned workflows atm:-

1. Mindomo > Workflowy > Inspire Writer > Word
2. Inspire Writer > Workflowy > Inspire Writer
3. Inspire Writer > Word > Inspire Writer

Programs involved:
Planning and Development - Mindomo, Workflowy, Inspire Writer
Writing - Inspire Writer, maybe some in Workflowy
Editing - Word, Inspire Writer

Storage formats - markdown, docx, OPML

General support program - Typora

I don't know about related note-taking and research. I'm sure wiki-links, backlinks, and tags will be core components, but haven't worked out a plan yet.

Though I have switched my newish formal zettelkasten project from Obsidian to Workflowy.  It lacks the nice Ctrl-hover that made Obsidian very fast when it came to position a new page; but that was only needed because the MOC with links was required to maintain folgezettel. Workflowy has folgezettel automatically, and the notes are immediately visible anyway.

I think Obsidian will remain a code editor at heart, with clunky features and a constant risk of workflows breaking - at least for the next few years. That doesn't make it something I can afford to rely on when I need smooth workflows. I think in 5-10 years time, it will either have improved massively, morphed into something else or be in terminal decline; atm I'm not confident that the first option is the most likely.

Workflowy has the requisite wiki-links, backlinks and tags but is an online database. That's okay for 95% of what I need. But I haven't checked out what it can do in this regard. It seems to be in active development, so hard to be too definitive about planning its use - it could get better (or worse); so far the newer features seem pretty well implemented.

Though I have switched my newish formal zettelkasten project from Obsidian to Workflowy
In fact, it's becoming my research/writing hub. I'd started by also having my small number of tasks etc there too (better to only use one program I thought), but I struggled to cope with that. Moved those to Dynalist (so that's no longer deprecated). Odd the way our minds work. What ought to be most efficient turns out simply irritating.

What Inspire Writer does it does okay. But no wiki-links, a limited tag system, limited search and no auto-complete. It could never be more than a small contributor to a system centred in another program.

Most of the other programs I have looked at in the PKM space are some way behind Obsidian, but I'm sure there will be more to come. The hybrid database/files model operated by Ulysses and IW has the potential to be very powerful.
147
Mini-Reviews by Members / Re: Inspire Writer
« Last post by Dormouse on March 03, 2022, 05:05 AM »
importing a long markdown document took much more time than i anticipated.
otoh, IW will only import one file at a time, so large files are still more useful than small ones.
148
Mini-Reviews by Members / Re: Inspire Writer
« Last post by Dormouse on March 02, 2022, 06:49 PM »
Typing [[ automatically generates a URL link.
...
doesn't recognise #tags, but has its own internal tag system
...
doesn't have highlight as such
...
Neither does it recognise strikethrough

If wanting syntax that works in markdown exported notes, the following works in Obsidian:
~[[wiki-link]]
~![[transclusion]]
~~~~strikethrough~~
==highlight== ; naturally ::==highlight in Obsidian and IW==:: highlights in both
@tags and #tags ; ~#tag works for beginning of line

I'm not sure what happens with a code export
''code block
Indents the contents and colours them in Obsidian and Typora
Nothing shows in source mode, and neither Obsidian nor Typora recognise the IW syntax if typed in directly
I don't need to know why. It may be useful. Possibly as an exportable comment.
149
Obsidian ... less inviting to use.
Workable but not smooth.
seems slightly clunky
Heading sizing has been re-done - ... I have tried adding some CSS overrides to avoid old themes from screwing it up, but ...
... Please report .. issues to the theme developer though.

The final quote is from the Obsidian developer in the forum, responding to a report that h1 headings had become gargantuan in the latest update. I think it sums up many of the issues that make Obsidian problematic for productive use. Things can change suddenly (it is still in beta, after all), sometimes break and that most users' workflow depends on a large number of developers, not all of whom are entirely up-to-date. Good program for fiddling, very responsive and flexible for programmers, but not the greatest for maintaining a smooth and productive workflow especially for the non-technically minded.

The contrast with IW is stark. In some ways that program is limited and rigidly not configurable. But everything is part of the whole and seems, so far, to be very reliable.
150
Mini-Reviews by Members / Re: Inspire Writer
« Last post by Dormouse on March 01, 2022, 04:45 AM »
Observations so far

I'd like folding, but understand that IW's design means multiple tiny blocks which can be shuffled. The groups and sheets are the equivalent of markdown headings and text. For me it's the equivalent of the Scrivener approach of starting with little bits, but that's the way it is. It does have an outline, and it does allow it to be used for navigation, though not reorganisation. It recognises any line starting with a # as a heading.

It's not bad at taking clips from the web. Images have to be pasted separately, but it's fairly seamless. Potentially makes IW quite a good inbox.

Generally fast, but importing a long markdown document took much more time than i anticipated.

Tables are straightforward (they don't exist in Ulysses at all).

The file splitting and merging functions are simple, effective and very useful.

Colour emojis appear in black and white when used. That's odd; makes it pointless to use them.

There's some fairly hinky behaviour with markdown and Obsidian syntax. Though I can see that some of it is actually useful:
  • It recognises any line starting with # as a heading.
  • Typing [[ automatically generates a URL link. Mmm. That seems to have stopped happening. That's good. But now it happens the minute the first closing bracket is typed. [[ ]] - but pasting it works.
  • Inconvenient behaviour like the above can be escaped by making it 'raw source' - that's putting a tilde (~) before the text. The tilde won't appear on the export, but the following text will.
  • Comments can be created with ++comment++ and comment blocks with %%. They don't show on export. This is useful.
  • It doesn't recognise #tags, but has its own internal tag system (same way Ulysses works). This means the tags exist in the database but not  any export. There are some advantages to that. @tags aren't recognised either but don't interfere with any other behaviour.
  • It doesn't have highlight as such. It has 'marked', using double colons before and after. Neither the highlight nor the colons are exported to markdown or plaintext, but are on export to rich text and docx. However, Ctrl-A, Ctrl-C followed by paste into any editor, does export the double colons, which can then be found and replaced. Again there are some advantages and disadvantages to this system.
  • Neither does it recognise strikethrough. Instead it has double pipes before and after. On markdown export, it applies the usual syntax; on rich text and docx export it strikes through the text; on plain text export the word disappears entirely.
Pages: prev1 2 3 4 5 [6] 7 8 9 10 11 ... 79next