Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jarusll
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Show HN: Tokri – a cross-platform drag-and-drop desktop basket
(github.com)
1 points
by
jarusll
9mo ago
|
0 comments
2.
▲
Show HN: Tokri – a desktop basket for temporary files, text, and images
(github.com)
2 points
by
jarusll
9mo ago
|
0 comments
3.
▲
by
jarusll
2y ago
I do agree the README was terrible. I've fixed it.
4.
▲
by
jarusll
2y ago
Dmenu like fuzzy search does make sense when you have alot of expansions. I'll add it as I find the need for it myself.
5.
▲
by
jarusll
2y ago
It is not meant to compete with feature rich programs. Keydogger does one thing and it does it well. If you think it's misbehaving in any way, it's so small you can read and confirm that behaviour.
6.
▲
by
jarusll
2y ago
Looked up `abbrev-mode` and that is a correct analogy. Abbrev mode also handles emojis, pretty cool. But then it's Emacs so I shouldn't be surprised. Offtopic, I wish my younger self followed RTFM when I used to use Emacs.
7.
▲
by
jarusll
2y ago
It works on Wayland as well AFAIK. I looked up espanso for expanding emojis and it seems they too use `wl-clipboard`
8.
▲
by
jarusll
2y ago
I do realise it now that it's missing it's usage. It's a simple keyboard macro which supports all printable characters for triggers and everything for expansions. It sends native key presses if all the expansion are printable
9.
▲
by
jarusll
2y ago
You get it perfectly. Being auditable was one of the priority which is exactly why it's small. Regarding the clipboard, it's a third party dependency. I looked into implementing Wayland clipboard myself but it is too deep Wayland.
10.
▲
Show HN: Keydogger – Minimal keyboard macro for Linux (Wayland)
(github.com)
97 points
by
jarusll
2y ago
|
43 comments
11.
▲
by
jarusll
4y ago
So indexing all the components and finding out all the interactions between them. This is exactly what class browsers do, they index all the classes and messages. The interactions could be described using an example/documentation. This
12.
▲
by
jarusll
4y ago
This is very well written. 1-3 describes my experience of tinkering in Pharo except I haven't actually built anything with it.
13.
▲
by
jarusll
4y ago
I love debugging and I would prefer this even if it's slower but there are cases where it's not easy to setup a debugger.
14.
▲
by
jarusll
4y ago
I would prefer LSP assists as mentioned above. I love having things within reach. I believe programming should be as painless as possible. Pharo(Smalltalk) IDE is one of the best IDE I've ever used. It even has a feature where you give
15.
▲
by
jarusll
4y ago
This is exactly what I would do ideally except I couldn't. I can understand that working in startups you would overlook alot of theory and due to hectic nature low quality calls(code/architecture explanation) are not appreciated.
16.
▲
by
jarusll
4y ago
Fixing bugs has worked out although I had to pull my hair.
17.
▲
by
jarusll
4y ago
1st is exactly what I do while reminding myself that I don't need to understand everything. Somehow for me it's easy to think like that in OO code and not FP.
18.
▲
by
jarusll
4y ago
Definitely a good advice. Profiling is something I haven't looked into and should be after debugging.
19.
▲
Ask HN: What are the ways you go about getting comfortable with a new codebase?
59 points
by
jarusll
4y ago
|
67 comments
20.
▲
Relation between Static Code Analysis and Discoverability
1 points
by
jarusll
4y ago
|
0 comments