#append — Public Fediverse posts

New post: The Markdown Link no. 12

Among today’s links are #markdowneditors Deepdwn and MarkLite, toolbar app Append, quick-capture app Kraa, and Mat Duggan plumbs the depths of the #filesystem

https://md-markdown.com/blog/markdown-link-no-12/

#markdown #Fountain #MSWord #WordStar #WordPerfect #Deepdwn #MarkLite #Append

New post: The Markdown Link no. 12

Among today’s links are #markdowneditors Deepdwn and MarkLite, toolbar app Append, quick-capture app Kraa, and Mat Duggan plumbs the depths of the #filesystem

https://md-markdown.com/blog/markdown-link-no-12/

#markdown #Fountain #MSWord #WordStar #WordPerfect #Deepdwn #MarkLite #Append

New post: The Markdown Link no. 12

Among today’s links are #markdowneditors Deepdwn and MarkLite, toolbar app Append, quick-capture app Kraa, and Mat Duggan plumbs the depths of the #filesystem

https://md-markdown.com/blog/markdown-link-no-12/

#markdown #Fountain #MSWord #WordStar #WordPerfect #Deepdwn #MarkLite #Append

New post: The Markdown Link no. 12

Among today’s links are #markdowneditors Deepdwn and MarkLite, toolbar app Append, quick-capture app Kraa, and Mat Duggan plumbs the depths of the #filesystem

https://md-markdown.com/blog/markdown-link-no-12/

#markdown #Fountain #MSWord #WordStar #WordPerfect #Deepdwn #MarkLite #Append

New post: The Markdown Link no. 12

Among today’s links are #markdowneditors Deepdwn and MarkLite, toolbar app Append, quick-capture app Kraa, and Mat Duggan plumbs the depths of the #filesystem

https://md-markdown.com/blog/markdown-link-no-12/

#markdown #Fountain #MSWord #WordStar #WordPerfect #Deepdwn #MarkLite #Append

Note to self, friends don't let friends #nconc lists returned from other packages in #emacs. nconc is a destructive operation which will break things in funny ways and #append will be just fine.

@foo

It's a little #clearer what's going on here if you put it this way:

>>> b = []
>>> b.append(b)
>>> b
[[...]]
>>> b is b[0]
True

So all you've done is create a #list, and then #append (not extend) that list to itself. Since `a` and `a[0]` are the same #object, the `in` test will return True either way.

@libreoffice It would be cool if you could design a strictly #append-only file format for documents, so that a #document consists of a sequence of #blocks that can be independently #hashed/#notarised. PDFs sort of work this way. At the moment, docs tend to get completely rewritten with every edit, meaning you lose #traceability to previous versions. You could achieve the same outcome by just appending the previous doc as an attachment to the current one, but that would get extremely inefficient as the number of edits increases.

@libreoffice It would be cool if you could design a strictly #append-only file format for documents, so that a #document consists of a sequence of #blocks that can be independently #hashed/#notarised. PDFs sort of work this way. At the moment, docs tend to get completely rewritten with every edit, meaning you lose #traceability to previous versions. You could achieve the same outcome by just appending the previous doc as an attachment to the current one, but that would get extremely inefficient as the number of edits increases.

@libreoffice It would be cool if you could design a strictly #append-only file format for documents, so that a #document consists of a sequence of #blocks that can be independently #hashed/#notarised. PDFs sort of work this way. At the moment, docs tend to get completely rewritten with every edit, meaning you lose #traceability to previous versions. You could achieve the same outcome by just appending the previous doc as an attachment to the current one, but that would get extremely inefficient as the number of edits increases.

@libreoffice It would be cool if you could design a strictly #append-only file format for documents, so that a #document consists of a sequence of #blocks that can be independently #hashed/#notarised. PDFs sort of work this way. At the moment, docs tend to get completely rewritten with every edit, meaning you lose #traceability to previous versions. You could achieve the same outcome by just appending the previous doc as an attachment to the current one, but that would get extremely inefficient as the number of edits increases.

@libreoffice It would be cool if you could design a strictly #append-only file format for documents, so that a #document consists of a sequence of #blocks that can be independently #hashed/#notarised. PDFs sort of work this way. At the moment, docs tend to get completely rewritten with every edit, meaning you lose #traceability to previous versions. You could achieve the same outcome by just appending the previous doc as an attachment to the current one, but that would get extremely inefficient as the number of edits increases.