Search
367 results for “czietz”
-
@ctietze Yes, there are some graphic glitches in Light Mode, similar to what you see with #OpenCoreLegacyPatcher installed machines.
I suppose the VM graphical rendering in not 100% ready for #macOS #Tahoe (probably due to the new #Metal version). -
@ctietze Yes, there are some graphic glitches in Light Mode, similar to what you see with #OpenCoreLegacyPatcher installed machines.
I suppose the VM graphical rendering in not 100% ready for #macOS #Tahoe (probably due to the new #Metal version). -
@ctietze Yes, there are some graphic glitches in Light Mode, similar to what you see with #OpenCoreLegacyPatcher installed machines.
I suppose the VM graphical rendering in not 100% ready for #macOS #Tahoe (probably due to the new #Metal version). -
@ctietze I think of #BQN as the answer to the question "what if an array language like #APL or J was also a normal programming language with lexical scope, first class functions, object-oriented programming with mutable state, and acceptable performance for scalar code?" (Scalar code means code with while loops and if statements, which is how you write procedural code in most languages and which is traditionally very slow in array languages.)
This normalcy of BQN makes it feel to me more general purpose than other array languages and it's pretty convenient as a go-to language that you use by default for most things.
-
@ctietze I think of #BQN as the answer to the question "what if an array language like #APL or J was also a normal programming language with lexical scope, first class functions, object-oriented programming with mutable state, and acceptable performance for scalar code?" (Scalar code means code with while loops and if statements, which is how you write procedural code in most languages and which is traditionally very slow in array languages.)
This normalcy of BQN makes it feel to me more general purpose than other array languages and it's pretty convenient as a go-to language that you use by default for most things.
-
@ctietze I think of #BQN as the answer to the question "what if an array language like #APL or J was also a normal programming language with lexical scope, first class functions, object-oriented programming with mutable state, and acceptable performance for scalar code?" (Scalar code means code with while loops and if statements, which is how you write procedural code in most languages and which is traditionally very slow in array languages.)
This normalcy of BQN makes it feel to me more general purpose than other array languages and it's pretty convenient as a go-to language that you use by default for most things.
-
@ctietze I think of #BQN as the answer to the question "what if an array language like #APL or J was also a normal programming language with lexical scope, first class functions, object-oriented programming with mutable state, and acceptable performance for scalar code?" (Scalar code means code with while loops and if statements, which is how you write procedural code in most languages and which is traditionally very slow in array languages.)
This normalcy of BQN makes it feel to me more general purpose than other array languages and it's pretty convenient as a go-to language that you use by default for most things.
-
@ctietze I think of #BQN as the answer to the question "what if an array language like #APL or J was also a normal programming language with lexical scope, first class functions, object-oriented programming with mutable state, and acceptable performance for scalar code?" (Scalar code means code with while loops and if statements, which is how you write procedural code in most languages and which is traditionally very slow in array languages.)
This normalcy of BQN makes it feel to me more general purpose than other array languages and it's pretty convenient as a go-to language that you use by default for most things.
-
@ctietze Yes, #Emacs has #org-babel thanks to #orgmode - I could see this being incredibly useful for non-Emacsians.
-
@ctietze Yes, #Emacs has #org-babel thanks to #orgmode - I could see this being incredibly useful for non-Emacsians.
-
@ctietze Yes, #Emacs has #org-babel thanks to #orgmode - I could see this being incredibly useful for non-Emacsians.
-
@ctietze Yes, #Emacs has #org-babel thanks to #orgmode - I could see this being incredibly useful for non-Emacsians.
-
@ctietze Yes, #Emacs has #org-babel thanks to #orgmode - I could see this being incredibly useful for non-Emacsians.
-
#Passivhaus … vielleicht etwas bereits gebautes dabei:
https://passivehouse-database.org/#k_Lehmhttps://passivehouse-database.org/#d_1899
mit etwas Literatur … :
Das Strohballenhaus von Benjamin Krick im südhessischen Seeheim-Jugenheim
https://passiv.de/downloads/07_20180814_Interview_Krick_Strohballendaemmung.pdfhttps://www.fr.de/rhein-main/darmstadt/stroh-statt-steine-11683567.html
Auf welche Kniffe es ankommt, erklären #GernotMinke und #BenjaminKrick in ihrem
Handbuch #StrohBallenBau | Dämmstoffe
2023 erscheint die vierte Auflage
https://www.baunetzwissen.de/daemmstoffe/tipps/buecher/handbuch-strohballenbau-1441277#Lehm
https://www.enbausa.de/projekte/passivhaeuser/passivhaus-aus-lehm.html -
@ctietze yes, it _is_ obvious to have a preview for mass text edit replacements. This is one of many reasons why I dumped #Emacs for #jEdit ~20 years ago.
Unfortunately, jEdit never became a full Emacs replacement, but close enough, and plenty of others since that have improved the art.
I've only recently re-adopted Emacs for #OrgRoam and it has been deeply frustrating. At best Emacs is an editor toolkit, and org-roam a #PKM toolkit, but I am persistent.
-
@ctietze A lot of my target use case hinges around this: how can I change the attributes of a character (name, gender, species, etc.) in a document without doing a potentially-catastrophic search-and-replace across the entire document? Preserving the character’s function and role within the work despite changing almost anything else about them.
In the #troff world you can do this pretty easily with the .ds macro to build a library of direct string substitutions.
\*[fuHERO] overcomes \*[paHERO] foe!
Perhaps there is a more native way to do it in #LaTeX than I have found; I haven’t researched it thoroughly. You can definitely set up data structures in #Emacs #lisp and pick out the attributes with #orgmode macros.
{{{fu(hero)}}} overcomes {{{pa(hero)}}} foe!
Here using `fu` for “full name” and `pa` for “gendered possessive adjective” (his/her/their/its).
In favor of #troff is the lower-level stuff. You can use macros to define strings en masse and then override individual choices for particularly weird characters. The downside is that you end up building up a library of macros to supplement your chosen package so that the main body of your document looks more like semantic than physical markup. And you probably need a #Makefile to assemble anything beyond a trivial document.
In favor of #LaTeX is mostly the higher-level stuff, and the short distance to semantic markup. #orgmode shortens this even further, and you can build your document in a single command (C-c C-e l p). But now the low-level stuff becomes annoying.
Perhaps with more research I can find the appropriate packages, but that may obviate the benefits of #orgmode altogether. Hopefully a well-fitting puzzle piece is out there, somewhere…
It’s all #tradeoffs but it’s not for paid work so I only have to worry about whether or not it works for me.
-
@ctietze A lot of my target use case hinges around this: how can I change the attributes of a character (name, gender, species, etc.) in a document without doing a potentially-catastrophic search-and-replace across the entire document? Preserving the character’s function and role within the work despite changing almost anything else about them.
In the #troff world you can do this pretty easily with the .ds macro to build a library of direct string substitutions.
\*[fuHERO] overcomes \*[paHERO] foe!
Perhaps there is a more native way to do it in #LaTeX than I have found; I haven’t researched it thoroughly. You can definitely set up data structures in #Emacs #lisp and pick out the attributes with #orgmode macros.
{{{fu(hero)}}} overcomes {{{pa(hero)}}} foe!
Here using `fu` for “full name” and `pa` for “gendered possessive adjective” (his/her/their/its).
In favor of #troff is the lower-level stuff. You can use macros to define strings en masse and then override individual choices for particularly weird characters. The downside is that you end up building up a library of macros to supplement your chosen package so that the main body of your document looks more like semantic than physical markup. And you probably need a #Makefile to assemble anything beyond a trivial document.
In favor of #LaTeX is mostly the higher-level stuff, and the short distance to semantic markup. #orgmode shortens this even further, and you can build your document in a single command (C-c C-e l p). But now the low-level stuff becomes annoying.
Perhaps with more research I can find the appropriate packages, but that may obviate the benefits of #orgmode altogether. Hopefully a well-fitting puzzle piece is out there, somewhere…
It’s all #tradeoffs but it’s not for paid work so I only have to worry about whether or not it works for me.
-
@ctietze If you want this behavior with #eshell, you should take a look at [eat](https://codeberg.org/akib/emacs-eat). It will handle these kind of programs properly and it's pretty fast!
Otherwise, you could vterm but you won't have support for #eshell. -
@ctietze From the #WWDC22 #SwiftUI Lounge:
Q: What’s the recommended way to use a @ViewBuilder for custom components: calling it right away in the init() and storing the view, or calling it later inside the body and storing the view builder itself?
A: We’d generally recommend resolving it right away and storing the view
Ref:
https://onmyway133.com/posts/wwdc-swiftui-lounge/#use-viewbuillder
-
@ctietze Nice, thanks! I would probably try #Obsidan primarily, I use #roamresearch as my daily #pkm at the moment but trying to migrate to local first.
Comparison-wise, Obsidian vs LogSeq, maybe try Roam vs Tana for a larger set of notes too. I'm more messing around than actively researching though
-
@ctietze I agree that highlights are often just a hook to the main source.
It's a shame #MoonReader doesn't exist on the Mac. (Though you could open in Mac books.app and then Search for the highlight blech.) -
@ctietze #MoonReader is good for exporting book highlights/notes. http://webseitz.fluxent.com/wiki/MoonReader
-
@ctietze Oh, z.B. Schleie freuen sich über einen dunklen Tank. Helle Tanks sind Stress.
Aber Spaß beiseite, ich weiß, was Du meinst.
Meine Besatzdichten waren ein Bruchteil vom in ökologischer Aquakultur Erlaubtem und lächerlich gegen konventionelle #Aquakultur. Für die Nährstoffversorgung der Pflanzen waren sie auch grenzwertig klein. Trotzdem hatte ich kein gutes Gefühl, was die Menge der Fische in der Wassermenge anging.
#Aquaponik
Wenn es soweit ist mit dem Land, kann ich #NoDig empfehlen. -
@ctietze Weißt du was? Wenn sie ein gutes Online-Interface haben, vielleicht noch Datenexport anbieten und wirklich die Kunden in den Mittelpunkt stellen, zahle ich sehr gerne pro Transaktion eine vernünftige Summe.
Wenn.
-
@ctietze you really tapped into a great guiding principle with that #atomicity blog post way back when. 🤝
-
@ctietze The Paint equivalent on #macOS has been #GraphicConverter since ever, hasn‘t it?
-
@ctietze Ich denke, die "Spielerei" *ist* das Werkzeug. Zotero oder Citavi u.a. bieten nicht die spielerische Möglichkeit des Fediverse, gleichzeitig eigenes Lesen, Denken und Erleben zum Ausdruck zu bringen, das zum Ausdruck Gebrachte zu verknüpfen und (!) sich potentiell unmittelbar mit anderen darüber auszutauschen. Die Aussicht ist verlockend, denn man setzt auf der Suche nach sinnvoller Interaktion mit anderen als Teil des Spiels (im Sinne #VilemFlusser) das #Zettelkasten-Prinzip um.
-
@ctietze @flyingmeat Using such a cute puppy for your evil commercial purposes is just… it’s a very nice puppy. Thumbnail: succeeded.
PS Looking at some of your old posts, is #TheArchive based on old code from #nvalt, or is it more a spiritual successor?
-
@ctietze Gemeint ist die von Sönke Ahrens beschriebene Arbeitsweise, die auch Niklas Luhmann angewendet hat. Quelle siehe Hashtag #Ahrens2017
