topbanner_forum
  *

avatar image

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

Login with username, password and session length
  • Wednesday November 12, 2025, 5:20 am
  • 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 ... 19 20 21 22 23 [24] 25 26 27 28 29 ... 79next
576
I learned something.  Never heard of transclusion before.  For any in that same boat: Transclusion
I knew it had to be a clever programming idea.
It's rather like the motor industry supply chain.
577
too off-topic
Too off-topic can't exist if you have made a link.
 :)
578
General Software Discussion / Tags
« Last post by Dormouse on May 28, 2020, 09:27 AM »
My thinking has evolved. As mentioned above, I believed it needed to be systematic to avoid the chaos of multiple tags for the same concept. I now believe that was wrong, at least for notes.

Any changes in tag names will simply reflect the evolving patterns of thought. So long as notes have links to other notes, there is always a route to older tags.This saves time on input and would systemically work rather like Zettelkasten structure notes.
Without the need to make them.
579
*[] Read all the Andy Matuschak references from Panzer
*[] Work out sequence for evaluating text editors
*[] Check out Typora, Obsidian,  Texts, HackMD and CodiMD

So how long before BBCode goes markdown? Or rather forums simply switch to markdown.
580
@wraith808, thanks. Are you using hackmd? Looks nice.

Yes, quite a bit.  So much so that I pay for it.  I'm writing my book in it (it has a book type layout), and I thought reading this thread the autolinking feature would be nice for this system.
I'll try this one out too, again within the limits of my PC time. I'll look at Texts too.
581
Obsidian is a powerful knowledge base that works on top of a local folder of plain text Markdown files:
https://obsidian.md/
This looks very interesting. I'll give it a go. When I can find time on a PC, since it doesn't seem to have an Android app.
582
So I am still struggling with one-note one-thought.  Specifically, what i think is one note ends up being a whole  bunch of thoughts. 

I'd recommend reading this set of links from Panzer. I've not read all of them yet,  but will. I've never read anyone whose thinking (so far) aligns so well with my own. I'm hopeful I'll find a useful addition to my own practice and, if not, it will be a nice ego boost.
Like me, he seems to be respectful of the way he believes Luhmann worked but sceptical of the the methods of his modern acolytes.
To paraphrase something I think you intimated earlier, the thinking is the actual goal, not the physical note.

I'll also point out that these are actual examples of notes.

Zettelkasten-like system used by Andy Matuschak:
https://notes.andyma...3ViqN3hh3SmrKzjQxWAr

https://notes.andyma...A1kDd46whJh2Gt5rAmfX

https://notes.andyma...SEBzTQiCVGoC4GfK3rYW

https://notes.andyma...FPTZSK3UmdsGExLRfZz1

https://notes.andyma...rQNKr6u7AZ1jFzfTVbMF

ED: I've now read his note on why books don't work. I sort of agree with much of it, but his understanding of the underlying science is over simple and he's looking out of his car to where he's going rather than taking time to see all the ideas on both sides.
So no longer completely aligned.
 :)
583
Which is a shame, as I would agree that such a feature would be good for acceptance of either MarkDown or AsciiDoc as somewhat of a replacement of WordPad in Windows. Perhaps even Word itself.
I think that's where the market will be and developers will always chase the market in the end. The major requirement is that there has to be a reasonably simple way of printing or publishing. The world hasn't gone completely digital. I still have clients who require hard copy and I suspect that many recent converts have been mostly motivated to avoid the snail and expect to print internally.
584
Zettelkasten-like system used by Andy Matuschak:
https://notes.andyma...3ViqN3hh3SmrKzjQxWAr
Thank you
Seems like a good day for having prejudices confirmed  8)

Maybe I should stop reading now
585
From an Ultraedit blog :
Markdown is a plain text formatting syntax aimed at making writing for the internet easier.
That fits with the way I see it, and there it succeeds. I'd use it for that myself with no qualms.
586
I'm not sure about document structuring.  What I do see is that the cursor position on the preview would have to be fed back to the hidden markdown document.  The commands and text would always only work on the markdown document. I  don't see why it couldn't work in theory but I doubt there's enough processing power on most Android machines to do it in real time. There's already a noticeable lag in preview update and adding the fro to the to would kill it.

Very nice to hear that there are other people with the same wish because it feels totally against this bit of the zeitgeist.
587
might be OK if I use text files and turn line numbers
OK so long as I use no commands, even italics. Using them seems to switch it to commonmark mode even if it later saves the file as txt. Makes sense as txt doesn't support italics so it does leave me looking ideally for an editable 'preview' mode.
588
AsciiDoc
Mentioning this has done me a great service. Used it as a search term on Google Play. No Asciidoc but new choices in Markdown editors. Commonmark. Seems to be far more configurable than the others.

I'm not sure I'd use it for writing,  though it might be OK if I use text files and turn line numbers off, but I'm hoping it will work well for formatting text files.

Has preview + edit and edit panel options. Someone suggested adding preview alone. I'm tempted to suggest making preview editable,  which would solve most of my issues. It's the only app I've seen which looks set up to do that because it has six symbol banks for commands,  four of which are purely down to individual choice.  And up to 30 symbols on each.
589
Personally,  I just write text. Bits of formatting added later. If needed... I don't care about document formats at this point and txt is fine.
Actually, I momentarily forgot the complete truth. I sometimes use italics and prefer to write them as I first type.

And, for some types of writing seeing and using markdown isn't a handicap.  Small part of what I'm doing at the moment though.
590
General Software Discussion / Text Editors
« Last post by Dormouse on May 26, 2020, 07:24 PM »
I've been thinking about text editors for programmers and comparing them with the equivalent for writers . And practicing typing by using a pen for writing on my tablet .

As a class, text editors seem stable, feature rich and highly functional; and there's a lot of them for all devices. Nothing similar for writers.

Having been thinking about Android and markdown, I'm moving on tothinking about the editing stage. I can't see anything on Android that would do. And, having thought about it, none of the Windows options I've ever used do what I'd ideally like either. I could design my own app but no feasible way of doing it myself and no obvious market : I read a piece today saying that all text editors were for programmers because editors for writers was such a tiny niche. Low level editing isn't a problem - plenty of options for that. It's the more individual, structured stuff I'm interested in. So I naturally wondered about trying an actual text editor. Search, find, long documents not a problem. Ditto splits, folds, compare, versions, simple stats. I assume that I can scrub the coloured language syntax, and I've seen at least one saying that it would be easy to set up my own scheme for text files.

Just wondering at this stage. I'm not up for long testing because I need to limit the time I spend on a PC. Thought I might look at Editpad Pro and Ultra Edit. Nothing I've seen is an obvious fit, but neither is anything else. I'd like a sophisticated bookmark system, comments and notes essential.

I'm assuming they'd be useless for markdown files because they'd insist on showing the markdown when I'd only want the text.
591
Ought to be clear that my main issue isn't with markdown as a file format  - though the lack of a truly accepted standard is an issue on its own  - but about the user interface usually presented. I do want WYSIWYG and often I'd prefer to accept a formatting choice rather than typing it. Depends on what I'm doing. I always need to focus on content and words.

From that point of view,  I hope the apps develop and improve rather than being part of a movement to change the way many users prefer to work.
592
Writing for the web is different. Fewer words, faster speed. And adding a bit of markdown can save faffing around later.
593
And possibly the key fallacy - Markdown is NOT readable.
It is decipherable but not readable.
Maybe it's different for programmers who are used to reading instructions mixed with content,  but for most people it's not readable even they have learned the instructions.
It would be easy to do a little experiment.
A markdown file with a few a variety of text formats and a few headings. And 3 nouns formatted red and a different 3 formatted green.
Take twenty subjects who have learned markdown: give half the markdown version and half the published version. Compare reading speeds. The next day ask them all to recall the red words and then the green.
I'm sure that the difference in reading speeds will be substantial and that those seeing the words in colour will have a much greater recall.

The implication is that formatting instructions mixed with text impair both reading and processing. I accept programmers may be immune.
Most writers have periods of reading what they have written interspersed with periods of writing. My case is that Markdown interferes with that.

Personally,  I just write text. Bits of formatting added later. If needed. Accepting Hemingway's maxim that writing should be separate from editing, if not the need to be drunk half the time. I don't care about document formats at this point and txt is fine. And text is what I want to look at,  not markdown instructions.

My need for WYSIWYG is during editing,  not writing. Then I need colour. And other things.  And I need to actually see it, not just have it identified.
594
Now for some of the evangelised fallacies. I read a tale of how txt is permanent but complex document formats aren't because ability to read them is lost over time. All his wordstar documents gone.
In reality,  I doubt he could still access his five and a quarter floppies, txt or not. Conveniently forgetting there's more than one encoding of txt.
And I bet I can find a way of converting his wordstar files,  whichever version they were.
And explaining that Markdown was simply txt and would always  be accessible.
Mmm.
I can imagine an Eureka moment in fifty years time when the Markdown archaeologist finally cracks an intractable file - "Ha, it's a Github flavour,  with the Joplin variations and additions! "
595
WYSIWYG was much-loved but not so easy to achieve. Home users loved it, using mice and GUIs.
... but programmers not so much. Possibly because they knew what it might hide. And they were keyboard warriors with masses of memorised shortcuts. Which saved them time as their hands never needed to leave the keyboard. Most journos too; early newspaper systems weren't great at GUI.

But that was never me. Despite using a typewriter since I was a child and teaching myself to touch type on one in my teens. Despite being a very fast typist. Most of the time my hands weren't near the keyboard and I was looking at the screen and thinking. When I was on the keyboard,  I was typing words.

But preferably not using a word processor. I've always avoided those for actual writing as much as I can. Nothing to help me as a writer,  many irritations interrupting my thinking. Liked outliners from the beginning because they gave a bit of organisation, faster access to my writing and irritated less.

The majority of people learned to use word processors at school and that's what was made available when they went to work. With  GUIs.
But programmers had their text editors,  keyboard shortcuts and numbered lines to help them navigate. And using them meant being used to working with syntax mixed visually with content.

And for my style of editing the mouse is faster than the keyboard.
596
Zettelkasten + LaTeX + VS Code = Productivity++ ?:
https://levelup.gitc...ctivity-a7deb650608e
That was an interesting read.
Who knows if it will prove a productive approach? Seems to me there's a lot of automating and not so much thinking, with multiple break points in the system. And he recommended zettlr for those who liked markdown.

And I noticed the next post down was 'How to be a keyboard warrior' - which brings me neatly to my next point:
597
The principal competition is a class of software originally developed so that secretaries could use computers to type and format letters,  documents and envelopes. Originally huge single purpose minicomputers. Probably the major usage that drove the expansion of the PC market. Then, with Windows, leveraged by Microsoft in its quest for dominance, it soon squeezed out desktop publishing. Being competitive required compatibility with Word formats and being feature rich.

The emphasis on formatting naturally produced complex document formats.
WYSIWYG was much-loved but not so easy to achieve. Home users loved it, using mice and GUIs.
598
As far as I can determine,  the major user community pre-evangelism was made up of web writers and programmers (and others used to working in text editors). Possibly still is.
This, I believe, explains how it has been developed. And some of the assumptions of the community.
599
I'll start with the major genuine advantage for markdown and plaintext generally,  and which often receives little emphasis: it is a relatively light user of computer resources. Memory,  bandwidth, processing power and programming. The shift online has given it a huge advantage.
600
I've decided that Markdown is a very bad thing for people like me
Mostly.

As presently incarnated.
I do realise that I need to explain my thinking - and it has taken quite a lot of thought as well as trying it out in many different apps - rather than just making a singularly bald statement. I considered giving it a thread on its own,  but the issues are part of the fabric of this thread and so it is probably best here.

I'll have to do it bit by bit though.  I'm too hungover with hay-fever to maintain any coherence in a single post.
Pages: prev1 ... 19 20 21 22 23 [24] 25 26 27 28 29 ... 79next