Nostr notes by Paul Bryan

Chatting with my son about a sort of #philosophy I suppose. In ...

2026-10-10T04:01:39Z

Chatting with my son about a sort of #philosophy I suppose. In particular, I shared this little bit of #python wisdom from PEP8 - Style Guide for Python Code

> A Foolish Consistency is the Hobgoblin of Little Minds [1]

Then I felt I should share the OG source from #ralphWaldoEmerson that also got the #OscarWilde treatment.

> A foolish consistency is the hobgoblin of little minds [2]

The reference [2] is a fun read, that includes some wisdom of its own.

> This page in a nutshell: Emerson's and Wilde's dismissals of consistency – often quoted out of context – do not refer to what so many people seem to think they do.

> Didn't read it? Don't quote it.

That last bit seems rather relevant these days with all the clickbait nonsense out there.

Also, I had a memory that #voltaire said something similar, but a cursory search didn't turn anything up. Anyone know of a relevant Voltaire quote? Maybe I'm just hallucinating though! I did however, discover lots more great quotes coming from Voltiare [3]

> One always speaks badly when one has nothing to say.

That hit close to home! I note in particular, that the quote makes no restriction on one to only speak badly when one has nothing to say, and I exercise that freedom regularly ;)

[1] https://peps.python.org/pep-0008/#a-foolish-consistency-is-the-hobgoblin-of-little-minds

[2] https://en.wikipedia.org/wiki/Wikipedia:Emerson_and_Wilde_on_consistency

[3] https://en.wikiquote.org/wiki/Voltaire

excellent! I was just trying things like this yesterday and ...

2026-09-10T12:25:59Z

In reply to nevent1q…jhud
_________________________

excellent! I was just trying things like this yesterday and didn't get a totally satisfactory solution - ended up just ssh in and use emacsclient in termnal mode. I did come across waypipe, but by then I really just needed to get some work done. Frustrating when work intrudes upon emacsing! I'll also give this a try tomorrow. Thanks for the tip 😃

Dear #emacs users. I like to use visual-line-mode and I also like ...

2026-08-14T12:22:47Z

Dear #emacs users. I like to use visual-line-mode and I also like to increase my font size a little. This results in help buffers, info buffers, ... looking weird due to the hard-coded line breaks at 70 characters (or whatever it is - I forget exactly).

In the screenshot, on the left there is a help buffer with unchanged font size and the hard wrapping fits fine. On the right, I've done M-x text-scale-increase and the hard wrapping breaks lines in weird places.

Question 1a: does anyone know how to get rid of the hard wrapping and just let emacs flow the text with word-wrap?

Question 1b: I was thinking of writing a minor mode which I'm thinking of calling no-hard-wrap to do it. My plan was to use a regex identifying a region that no-hard-wrap operates on. So for a helpful buffer, it would just operate on the region delimited between the heading Documentation and the heading References. In that region, if there is a line break followed by a non-space character, then I want to suppress the newline.

So, any tips for how to where to look for #elisp to alter a buffers display like that? Would an overlay do the trick? Make such newlines display as zero-width space or something?

EDIT: It should just be a regular space not a zero-width space.

That does seem to explain it. Your screenshot shows what should ...

2026-08-14T11:50:11Z

In reply to nevent1q…w7ma
_________________________

That does seem to explain it. Your screenshot shows what should be the correct behaviour. The 3rd block works because the value is taken from the interpreter's last statement output. All others are the correct behaviour. Number 1 needs an explicit return.

This screenshot I think shows how to make all of them output.

must be something to do with this excerpt from the.org manual ...

2026-08-14T11:36:43Z

In reply to nevent1q…22lm
_________________________

must be something to do with this excerpt from the.org manual

> When evaluating the code block in a session (see Environment of a Code Block), Org
> passes the code to an interpreter running as an interactive Emacs inferior process.
> Org gets the value from the source code interpreter’s last statement output. Org has
> to use language-specific methods to obtain the value. For example, from the variable
> _ in Ruby, and the value of .Last.value in R.

https://orgmode.org/manual/Results-of-Evaluation.html

There should be a python repl in a buffer where the evaluation is taking place. I forget how it's named, but something like *...python...* You could look there and see if that has anything useful

I use paru and it shows me the diffs from the previous version! ...

2026-06-23T23:18:51Z

In reply to nevent1q…40rn
_________________________

I use paru and it shows me the diffs from the previous version! Usually it's just a version number bump and change to the SHA hash. It's quite quick that way. Very handy. I also only use a handful of packages.

I always check them

2026-06-23T22:11:23Z

In reply to nevent1q…lpqj
_________________________

I always check them

If you're not going to check the PKGBUILD's, then ...

2026-06-23T21:57:37Z

In reply to nevent1q…w2ap
_________________________

If you're not going to check the PKGBUILD's, then it's not safe. Never has been. The risk now is probably lower than it has been recently though. Maybe even lower than before the recent attack, what with the extra scrutiny.

My advice is to wait until you're not tired, and then check the PKGBUILD's. Ask for help if uncertain about something.

perfect response 👏

2026-04-23T22:04:16Z

In reply to nevent1q…jrg3
_________________________

perfect response 👏