dharmik
@dharmik@linuxusers.in
admin @ linuxusers.in.
student. custodian of useless trivia.
hacker. python. c. unix. vim.
student. custodian of useless trivia.
hacker. python. c. unix. vim.
Location: 23.014509,72.591759
81 following, 28 followers
dharmik
@dharmik@linuxusers.in
Location: 23.014509,72.591759
81 following, 28 followers
- mail at dharmiik [at] proton [dot] me
- i occasionally post in long-form at: https://dhrm1k.github.io
@dharmik I feel like unless you're packaging for Debian there's no point on using Debian for python packages
@crmsnbleyd @dharmik better than running out of space because too many virtualenv. Idk how disastrous pip user install has become since that extra flag thing
https://dhrm1k.github.io/experimenting-with-stable-diffusion.html
You know, I discovered Aladdin the same way 🙈. Check this.
i guess I like musicals.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Trailing_commas
every core unix command I use
https://wizardzines.com/comics/every-core-unix-program-i-use/
Alt...
## basic file stuff
touch - create file
mkdir - create directory
cp - copy
mv - move
rm - delete
ln - create symlink
ls - list directory
## how big is it
wc - word count
du - file size in bytes
df - filesystem usage
## slice & dice files
sed - replace regex
tr - replace character
grep - search file
cut - get column
awk - get column (+ more)
sort - sort lines
uniq - unique lines
head - first 10 lines
tail - last 10 lines
## filesystems
mount - mount a filesystem
umount - unmount
dd - copy data to a disk
## manage processes
ps - list processes
lsof - list open files
kill - send a signal
pkill - fancy `kill`
top - who's using CPU?
uptime - time since reboot
## permissions
chown - change owner
chmod - change permissions
## time stuff
time - measure runtime
date - current time
sleep - wait X seconds
cal - cute calendar
## useful with pipes
less - scroll text
cat - print file contents
tee - stdin -> file + stdout
xargs - run cmd for each line
find - find files by name
## compression
tar - make/extract tar files
gzip - compress with gzip
gunzip - decompress
zip - compress with zip
unzip - decompress
## & more
which - find cmd on PATH
man - read man page
crontab - edit crontab
md5sum - calculate md5sum
diff - diff files
where this came from was really just I ran `history` and I wondered if everything I used that felt like a "core unix tool" would fit on one piece of letter paper and it seemed to fit
@b0rk I suppose the "official" definition of "core unix tool" would be the ones defined by POSIX (https://pubs.opengroup.org/onlinepubs/9799919799, specifically the list of utilities in https://pubs.opengroup.org/onlinepubs/9699919799/idx/utilities.html)
Though that doesn't really matter that much. This seems like a good list of commands to know.
@b0rk I wonder: How far back in your history did you look to make this list? I guess it would be many days, not only a few.
also a couple of people asked about networking tools so here is “every networking tool I know” from a few years back
(which for some reason includes several tools that I have never used)
https://wizardzines.com/networking-tools-poster.pdf
@b0rk realpath ?
@gduchaussois sounds like it would be useful in theory but I’d never even heard of it!
@b0rk I guess it's more useful in scripts where you want to know where the "real" file is because it gives you information in the full path
https://allpoetry.com/poem/17487308-Delusion-Angel-By-David-Jewell-by-ColinT1
#emacs #unix Miscellaneous notes on reading @ramin_hal9001 https://tilde.town/~ramin_hal9001/articles/emacs-fulfills-the-unix-philosophy.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-01_emacs-is-an-app-platform.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-02_what-is-the-unix-philosophy.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-03_unix-is-lesser-fp.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-04_lisp-does-fp-better-than-bash.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-05_unix-and-lisp-history.html
https://tilde.town/~ramin_hal9001/articles/emacs-unix-06_rebutting-critiques.html
For starters, excellent early history showing that unix and lisp are not direct relatives.
One small note that occurs to me is that in Mashey and Kernighan '84, they point at unix's shell's success at stopping people more C. 1/?? (but two for my purposes here)
@ramin_hal9001
In contrast, in the revised article presenting gnu emacs, it is a stated goal to get secretaries who were not trained as programmers an entrypoint to begin writing lisp. This is echoed by a much later essay by Strandh noting that lisp, moreso than other languages has a bunch of self-taught eccentrics [].
@ramin_hal9001
3 / >2
I think it might be worth clarifying writing elisp defuns, which I identify with programs, and the practice of writing emacs major and minor modes.
@screwtape @ramin_hal9001
Nice series of articles.
I would add that both emacs and unix were created to get a job done (both were *originally* about comparatively simple text processing), and had a lot of ad hoc elements to that end, which are awkward to say something cohesive about. It's easier to talk about things that had some over-arching goal to start with and that stuck to that goal/philosophy at all costs -- not that such things happen very often, at least not successfully.
> gnu emacs, it is a stated goal to get secretaries who were not trained as programmers an entrypoint to begin writing lisp.
I can't tell if you had it in mind, but (as is well-documented) Unix began as a system for secretaries. Well, that was their official excuse anyway. :)
I let "hackerpoetry.com" expire yesterday after having it for decades and never doing anything with it. Hopefully it finds a better home.
STORAGE is a Medley Interlisp tool that shows a bar chart of the amount of storage allocated to each Lisp data type. The black part of a bar represents the number of items or pages currently in use, the gray part the number of free items or pages.
#interlisp #lisp #retrocomputing
Alt...
Screenshot of the black and white desktop of a 1980s graphical workstation environment. The desktop has a gray background pattern and some windows with a white background and a title bar with white text on a black background. The main window shows a bar chart laid out horizontaly. Each bar has a black and a gray part and a text label next to it.
My design goal on websites is that bright young teenagers could learn HTML and CSS with the "View Source" button without having to decipher obfuscated code that looks like it's meant to summon a Lovecraftian horror.
@amin yes.
this is the way.
I don't wanna be a web dev, I wanna be a spider, spinning a lightweight but strong web. ;)
Hmmm, what if if it spins backwards?
It travels backwards in time.
@amin worthy of a follow ESPECIALLY given your wonderful avatar.
Haha, I appreciate it! I drew it in pure HTML/CSS, years ago. ;)
https://codepen.io/benjaminhollon/pen/pogVzbY
I then ended up turning it into a live coding demo with editable source on an old version of my website.
Edsger W. Dijkstra (1975):
"The tools we use have a profound (and devious!) influence on our thinking habits, and, therefore, on our thinking abilities."
I hear you like dialogs and property sheets, so here goes. This is the TEdit rich text editor of Medley Interlisp with an open document and the free menus (i.e. dialogs) for controlling text attributes, paragraph formatting, page layout, index and TOC.
#interlisp #lisp #retrocomputing
Alt...
Screenshot of the black and white desktop of a 1980s graphical workstation environment. The desktop has a gray background pattern and some windows with a white background and a title bar with white text on a black background. The main window shows a document open in a word processor. Above the main window, one above the other, are 4 dialog boxes for controlling various properties of the formatting and layout of the document.
@dharmik did a GSoC with Inkscape way back in 2012.
@dharmik #Inkscape required that you fix two bugs. I think I must have fixed two bugs from the bug tracker, and then chose one of the GSoC projects and wrote a proposal.
My GSoC was successful in the sense that my mentor and I did some work on the guidelines in Inkscape. Was able to get some understanding of the codebase. Unfortunately, by the time the project ended, the code was no where ready to being merged, and I went into full time university. I was not able to regularly contribute to Inkscape after that. Ideally we should have chosen a project that could be merged within two months.
My mentor was nice and supportive. Had a great experience overall. Learnt a lot. I think I was the first person to build Inkscape with clang++. Made a small patch that allowed Inkscape to be built with that compiler.
I definitely would like to contribute to Inkscape some day...
