I'm going to have a lot of fun converting my old Mac-only documents like .rtfd and documents in the iWork suite. :P
(At least .rtfd is literally just an .rtf file and a directory for images)
Random aside, the modern mac .rtfd format reminds me a LOT of the classic mac "TeachText" format, which used a plain text file as the text itself, but used the #ResourceFork of the file to store images.
So the files looked like they were rich text because they had headers in a larger font than the rest of the body, but it was really just plain text with bitmap headers ;)
The Resource Fork was something really unique that the #ClassicMacs did. I haven't seen anything like that today. Even modern macs just use a directory and the GUI makes you think that it's a file (but the command line shows a directory).
One of the reasons I love tar is that you can compress all the files as a single data stream, rather than compressing files individually. That really saves a lot of space when there's similarity, or very small files.
The only GUI archiver I ever used that had that option was 7zip.
@RL_Dane@sotolf@joel@pixx
It wasn't even a contest, though—the Windows-compressed versions were half the file size. You'd think they could, maybe, compress for speed while the program's open, then on the final save before close compress better?
I still kinda like the idea behind the crazy iWork spreadsheet -- instead of having 1024x1048576 or however many empty cells to work with, you only get as many cells as you need for what you're doing. It works slightly more like tables in word processing documents instead of a huge blank canvas like most spreadsheets. (But it's functionally the same, and you're not limited to a certain page size)
@RL_Dane@sotolf@joel@pixx
My parents weren't married yet, maybe not even dating (can't remember when they started). ;)
They got married in 2000, I think. I know they moved to Afghanistan in mid-2001 (they've got stories about the evacuation right before 9/11). I was born three years later in '04.
Not really where I'm going with cal, but that looks fascinating! You just point it to a CalDav URL and it can show you your calendar entries? So you could use it instead of Thunderbird for your appointments and such?
@RL_Dane@joel@sotolf@pixx
Well, actually, khal reads from a local directory, but vdirsyncer, developed by the same team, will read your CalDav to that directory. I'm able to use the same directory with todoman. I also use it with CardDAV via their other utility, khard.
@RL_Dane yes but it needs vdirsyncer to work, vdirsyncer does the heavy lifting by talking to the dav server and storing the data in vdirs, from there khal can read those
If you want to script it, it can be done. I guess you could accept n>1 parameters, assume that $1 is the month, and everything else are days, maybe use run something like sed 's/'"$day"'/ ./' against the cal output.
It's for when I have a writing project I don't have a finalized name for yet or when I just want to mess around; it'll create a file for me, let me scroll through them and see the content to select one, etc. The one thing I still want to implement is some form of easy migration to my standard write script's time and wordcount tracking.
Best bet is to move those functions to a separate file that can be sourced by several of your scripts.
It makes reading the script by others kind of a pain, though. Then they have to hunt through your repo for that extra source file and figure out which functions you're actually using.
I do like the use of fzf, though. I've started using that in some of my scripts, especially my journal one.
@RL_Dane@joel@sotolf@pixx@mirabilos
Yeah, I have a journal script too and I want to use fzf for it.
What I want to figure out is some way to search by the previewed content of the file, and not just by the non-descriptive filename. But having the preview is a good start.
@RL_Dane@joel@sotolf@pixx@mirabilos
No, it just uses cat, but it displays it when you've got your selection thingy on an entry. Try it; go to a directory with some markdown files in it and run fzf --preview 'cat {}'.
I probably could use something like glow for the preview, though.
@RL_Dane@joel@sotolf@pixx@mirabilos
You can pipe whatever you want searched to fzf. I've tried solutions that pipe each line of every file to fzf, separated by a : so you can still separate the filename from the output, but it doesn't look great.
Hmmm, then it looks like the only solution would be a janky one involving a temp directory with symlinks --
do the grep for the search term first, grab the list of matching files, create a temp directory with symlinks to the files that matched, and then fzf from there.
--ansi can parse color codes, so I can use that for styling
--nth and --delimeter can control which fields are searched (and how they're separated)
I could use --bind 'enter:become(echo {2})' to, say, only return the second field from the selected entry.
I passed the --ansi option, so I can do some formatting to make things clearer, but I haven't bothered yet. The thing I did was pass the cat output to xargs to remove newlines and tabs, then used tab as a delimiter for the fields.
@RL_Dane@benjaminhollon@joel@sotolf@pixx@mirabilos i do that in neovim/vim. I configured it a way to search through a list of predefined directories. I'm using vimwiki, and there is a way to have journal files there too, and everything with fzf ;)
@RL_Dane@joel@sotolf@pixx@mirabilos
Okay that surprises me, since it's developed by Charm and they've really made a name for themselves in developing CLIs.
@joel@RL_Dane@sotolf@pixx@mirabilos
Because that's the point of this script; I don't have a descriptive name for the writing project yet, so it sticks it somewhere with an id as the filename and facilitates opening and editing the one I want. Then (ideally) I'll be able to migrate that to a final location once I know the name I want.
Add comment