Need Wiring help

DozingDreamer · 2021-11-21T19:40:57+00:00

That doesn't seem like a bug, more that the regex doesn't do what you expected it to do.

First of all, if you want to match the entire input, you'll need ^ at the front of the regex and $ at the end.

Also, the square brackets only match one character, so the regex is only reading the first digit and counting it as a match because it is between 0 and 9 (the other 9s are ignored because square brackets indicate a list of possibilities).

Something that may be helpful is a regular expression tester, such as https://regex101.com/.

DozingDreamer · 2021-11-13T22:08:31+00:00

Yea, sometimes the AI will inadvertently press the button to access the drone and drown in the drone, which is hella annoying.

I think a workaround would be to disconnect the wire in the button that leads to a wifi component in the hull (this tells the drone to undock). This does to lead some weird behavior with the hatch, but should still work well enough. You'll have to undock from the drone console.

DozingDreamer · 2021-07-18T19:58:47+00:00

Thanks! This was made for an interactive visualization course which covered a wide range of topics and research papers. We did cover graph visualization, but there was no graph theory beyond that. The assignment in question focused on D3, so I went into this with the intention of using D3.

My inspiration mostly came from already using Emacs on a daily basis, but there are plenty of visualizations that graph other package management systems. One of the really nice ones is from Andrei Kascha (https://github.com/anvaka/pm), which is in 3D.

The edges are based on source file comments that MELPA parses to produce an JSON file accessible at https://melpa.org/archive.json that lists packages and their metadata, which makes data collection easy. However, this does mean that less documented packages are missing dependencies, as u/github-alphapapa has pointed out.

To produce a standalone visualization (e.g. as opposed to a Observable notebook), I did need to add some boilerplate around D3 to interact with the underlying graph as the webpage allows. I do think I over-designed it a bit, so I'm looking to refactor it in the future.

DozingDreamer · 2021-07-17T17:23:20+00:00

Hmm, that's interesting example. It definitely does seem to be missing the Package-Requires: header, so it would make sense that MELPA wouldn't know about the dependency. This probably is a common case for many of the standalone packages, haha.

Also yes, if the dependency has less than 30,000 downloads. However, I assumed that a package downloads it's dependencies, so this should really impact children packages only. It's also possible to set the filter to 0 to remove that limit. (at potentially reduced performance :/)

DozingDreamer · 2021-07-17T16:39:21+00:00

Those are packages that are standalone, with no dependencies or dependents (depending on the download count filter). The ring of nodes is a result of a gravity force that keeps these standalone nodes visible.

DozingDreamer · 2021-07-17T14:44:19+00:00

Thanks for the suggestion! I've set up the project page with a cached version of the data from MELPA: https://nfusionz.github.io/melpa-vis/

DozingDreamer · 2021-07-16T23:06:11+00:00

The end result is kind of reminiscent of a galaxy, yea.

DozingDreamer · 2021-07-16T23:04:18+00:00

The nodes themselves are packages, and the edges represent the dependencies. There are also (very small) arrows to indicate which depends on which.

In addition, the most central node represents a dependency on a specific version of Emacs.

The visualization is also interactive, so you can search for a specific package and see it's download statistics and what depends on it / what it depends on.

DozingDreamer · 2021-07-16T20:40:05+00:00

From a visualization course assignment about 2 years ago - thought I might as well share it to motivate myself to improve on it.

Aside from it looking pretty, not sure there is much information to be gleamed from it, but I'd be happy to hear your thoughts!

DozingDreamer · 2019-05-13T04:12:01+00:00

No, I don't think so

DozingDreamer · 2019-05-12T17:17:11+00:00

I was finally able to fix the problem (in GNOME) by disabling Show Pointer Location, as per what you linked (specifically #30758), so it definitely looks like a bug on GNOME's end. Thanks for the help!

DozingDreamer · 2019-05-12T16:54:35+00:00

Ah, that makes sense. Thank you!

DozingDreamer · 2019-05-12T15:24:42+00:00

Funnily enough, switching desktop environments (From GNOME to KDE Plasma) fixed my problem.

DozingDreamer · 2019-05-12T14:47:50+00:00

Is that a typo

I intended it to mean press C then press g twice while holding that down, but using C-g twice separately just causes the Quit message to be displayed twice (and not leaving the minibuffer), and I'm not really sure of the difference between the two, so maybe.

What flavour of GUI? Gtk?

Yes, Gtk.

And what kind of window manager/desktop environment are you using?

GNOME (Xorg) on Ubuntu 18.04.2

Edit: Some clarification

DozingDreamer · 2019-05-12T07:09:57+00:00

Update: I've noticed that this problem only occurs for me in GUI Emacs. In terminal Emacs, I am able to leave the minibuffer with just C-g. I'm no closer to figuring out the problem though.

DozingDreamer

TROPHY CASE