geek.log

A log/todo-list re: things I want to do with grex, gopher, qutebrowser, vim, and other linuxy contrivances.

A reminder to myself: while rolling my own html is fun in a tedious way, there are much more interesting things to learn/ work with. This log serves as a progress/hurdle dump which is public. I do not want to flood it with its own creation.

Devise a satisfactory toolchain that updates this; it’s quite alright if it pumps out questionable html or markdown.

meta.geek.log

• push done logs to the top; TODOs to the bottom.
• devise a stylesheet/guideline for writing this log.
• devise a toolchain to publish html with minimal work:
  • convert to html –> apply stylesheet –> push to public_html
• devise a toolchain to publish to gopher:
  • push to public_gopher ?
• clearly, the markdown that is hand edited for html will not suffice for the gopher. Options:
  • drop one of the two.
  • restrict one of the two to some purpose: publishing logs, and/or informative articles.
  • make the purpose of the log rudimentary.
• perhaps …. have a log for each purpose?

  • For ex: vim is easy to pick up based on my need; and this section is the fastest growing. A single command with a tag, that appends to the appropriate log files; which can later be assembled and published as necessary.

  • keep in mind: implement the easy viewings of such a conglomerate of log files under one header: there’s a very nice effect upon viewing such agglutinated progress.

  • besides the logs of a LOT more pursuits can be added other than this one. labradoc redux.

  • jrnl.sh does serve this purpose, though I think I’d like to give a bespoke solution a shot!

i3:

• Make i3 recognize the volume buttons!
  • XF86_________ something something. I can’t keep pulling up alsamixer or pavuctl every time ffs.
• i3lock on lid close.

GOPHER:

• create menus for the gopher folders.
  • (menus are these explanatory banners/texts that head each gopher folder)
• should I host my todos on gopher?
  • well, am I not doing it already?
• migrate the labradoc changelog on gopher.
• migrate the blogs to gopher.
• set textwidth of gopher:
  • full lines seem to lose a character or two when viewed in gopher: need to wordwrap.

GREX:

• colors for the grex bash.
  • Somehow I need to invoke bash again for these colours to be effective: the default login does not seem to apply .bashrc.
  • I have added /usr/local/bin/bash to .profile – this executes bash upon startup, where I have colours and pwd in the prompt. This means I have to exit twice to logoff FIXED
    • Prefixing exec with the bash path in .profile replaces the current shell instead of invoking and nesting. A single logout works!
• colors for ls; indicating types of files: dirs, executables, etc.
  • ls –color=auto/always ought to do it?
  • ls does not seem to accept –options. vim does. why?
• get the prompt to display pwd. DONE
  • it’s complicated, refer to PROMPTINGS under man bash
• mkhomepage? (not too enthused – not very inclined to learn HTML)
  • (perhaps a mirror of the tilde.town pages?)

ftp/scp/nc/netcat/rsync:

• find/learn a protocol to push/download files. DONE:

  • use scp instead.

    scp sourcefile login@host:/path/to/destination/file scp login@host:/path/to/source/file downloded_file_name

• How do you access the local system from within a login session?

  • ssh -Rports is a solution where ports are reverse forwarded from the remote machine to the local machine.
  • needs: a) port forwarding on router, b) public/static IP. That’s a battle for another day.

• SSHFS : sort of solves the above problem by mounting the remote system as fuse. Way more convenient for transfer:

   sshfs <username>@host: /path/to/mountpoint
   fusermount -u /path/to/mountpoint
  

HTML:

• I now have a homepage @ o quite pedestrian !!
• Had to cook up some html; cannibalise some more from arcturus.
  • I like it; but it has to be an occasional thing: it feels purely cosmetic.
  • I think gopher will be my main driver. the response here @grex is slow though. can anything be done about that?

• Retrieve labradoc as a markdown file: DONE

   pandoc -s -r html http://labradoc.com/i/zzalpha/p/just-a-log -o justalog_pandoc.md
  

• Convert markdown file as html: DONE

   pandoc justalog_pandoc.md -t html -o justalog.html
  

  • Although it must be said that markdown source.md > destination.md does a better job than pandoc out of the box. More pandoc research?

• index.html houses the default text/links for each directory.

• post links from index.html: DONE

    <a href="link_address"> link_text </a>
  

• restrict width, color, background-color … check the files.

• pandoc/markdown html creation with custom stylesheet/CSS?
• separate background-colors/sizes for code snippets?

QUTEBROWSER:

• redirect gopher:// links to a terminal with lynx. or VF1.
• codedojo for learning the commands better.

• unbind d, bind dd to close tabs. DONE

    config.bind('dd',tab-close)
    config.unbind('d')
  

  • the same can be done by :bind and :unbind, but these do not persist across sessions.

VIM:

• learn shifting lines/blocks of lines (that is not the VISUAL mode) DONE
  • m dest_line_number
• do vimtutor or that vimgaming website.

• markdown: syntax colouring: DONE

    :set syntax=markdown
  

• would like something to do with automatic list continuation upon pressing enter.

• !insert_your_command helps run compiles/renders within vim.
  • How do I save and execute an external command in one shot?
    • autocmd BuffWritePost something something.

MARKDOWN:

• Use nested lists over comments.
• See if custom styles work with markdown: mainly need to set max-textwidth.
  • no they don’t. prefixing the html files with the styles works though.

SHELL:

• shorcuts for invoking firefox (ff) and firefox private (ffp): DONE
• tty: autorefresh upon quitting vim or less. currently need to Ctrl+L.

LINUX:

• something to do with battery performance.
• automatic mounting and unmounting of sshfs filesystems.

OBSERVATIONS:

• Learn to link symlinks. Do symlinks work with gopher?
  • yes they do.
• I have 100MB of space allocated.