Search
241 results for “czietz”
-
@ctietze store the secret in a safe place (derived from TPM2, /var/lib/systemd/credential.secret, …) and pass it along to the service using systemd's credentials capabilities:
https://systemd.io/CREDENTIALS/ -
@ctietze Ich brauche sie fuer den Kippmechanismus meines #NeXT #MegaPixel Display (mini) Nachbau.
-
@ctietze @younata Alas it is more complicated than that. #expect() predates (slightly) the introduction of move-only types. The technical constraints preventing us from relaxing the relevant argument types to ~Copyable are… complicated.
We're planning to refactor #expect() entirely in order to resolve the problem, but we likely need to wait for Borrow<T> to land among other compiler changes.
-
@ctietze @nikitonsky I've switched to the Alabaster themes a few weeks ago, too. The comments being more prominent is one of the reasons I've stuck with it. #alabaster #HelixEditor
-
@ctietze I need to be able to make slides from #OrgMode files. But #Beamer cannot (and will not) be made to produce #taggedPDF output (thanks, @mxp). So rather than bang my head against #TeXLaTeX, I took a step back.
Check this out:
pandoc why-yes-i-am-a-wizard.org -o why-yes-i-am-a-wizard.pptx && soffice --headless --convert-to pdf why-yes-i-am-a-wizard.pptx
https://help.libreoffice.org/latest/en-US/text/shared/guide/start_parameters.html
No Haskell noodling required.
-
@ctietze I need to be able to make slides from #OrgMode files. But #Beamer cannot (and will not) be made to produce #taggedPDF output (thanks, @mxp). So rather than bang my head against #TeXLaTeX, I took a step back.
Check this out:
pandoc why-yes-i-am-a-wizard.org -o why-yes-i-am-a-wizard.pptx && soffice --headless --convert-to pdf why-yes-i-am-a-wizard.pptx
https://help.libreoffice.org/latest/en-US/text/shared/guide/start_parameters.html
No Haskell noodling required.
-
@ctietze I need to be able to make slides from #OrgMode files. But #Beamer cannot (and will not) be made to produce #taggedPDF output (thanks, @mxp). So rather than bang my head against #TeXLaTeX, I took a step back.
Check this out:
pandoc why-yes-i-am-a-wizard.org -o why-yes-i-am-a-wizard.pptx && soffice --headless --convert-to pdf why-yes-i-am-a-wizard.pptx
https://help.libreoffice.org/latest/en-US/text/shared/guide/start_parameters.html
No Haskell noodling required.
-
@ctietze I need to be able to make slides from #OrgMode files. But #Beamer cannot (and will not) be made to produce #taggedPDF output (thanks, @mxp). So rather than bang my head against #TeXLaTeX, I took a step back.
Check this out:
pandoc why-yes-i-am-a-wizard.org -o why-yes-i-am-a-wizard.pptx && soffice --headless --convert-to pdf why-yes-i-am-a-wizard.pptx
https://help.libreoffice.org/latest/en-US/text/shared/guide/start_parameters.html
No Haskell noodling required.
-
@ctietze I need to be able to make slides from #OrgMode files. But #Beamer cannot (and will not) be made to produce #taggedPDF output (thanks, @mxp). So rather than bang my head against #TeXLaTeX, I took a step back.
Check this out:
pandoc why-yes-i-am-a-wizard.org -o why-yes-i-am-a-wizard.pptx && soffice --headless --convert-to pdf why-yes-i-am-a-wizard.pptx
https://help.libreoffice.org/latest/en-US/text/shared/guide/start_parameters.html
No Haskell noodling required.
-
@ctietze I've had the same experience. In the large project I work on, #Xcode rename fails more often than not, while LSP rename (in #ZedEditor) works and is very fast.
-
@ctietze @bignose @mcr314 May be #calcurse is an option. https://www.calcurse.org/ My tool of choice is a mixture of org and nextcloud, but pure cli calendar with ics manipulation should be possible with calcurse. Another option with optional emacs integration is #khal https://khal.readthedocs.io/en/v0.8.4/usage.html
-
@ctietze @simon_brooke Of course we have to mention #JabRef We use #bibtex as primary format and are completely open source.
And we also have support for pushing citations to #emacs
-
@ctietze many things in many scripts, shell functions for my
#zettelkasten , #johnnydecimal system too and everywhere where I can 😅 -
@ctietze @mjog If I remember things correctly, the #eglot also uses Eclipse language server.
Tried this thing a year (or two) ago, found that I need to edit some ugly Eclipse-specific XML to setup my favourite coding covention — and stayed with #IDEA :dragnsad:
Also I met the same problems like in original post.
Will be happy to check this new server! 1-2 yrs ago there were only Eclipse and discontinued :dragnsad: #Jetbrains language server (cos they want the IDEA as first class citizen?)
-
@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 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 The Paint equivalent on #macOS has been #GraphicConverter since ever, hasn‘t it?
