The Command-Line Office
51–60 of 67 posts
Re: The Command-Line Office
#52Re: The Command-Line Office
#53I have aliases defined to reach these subdirectories because I am lazy:
# calcurse stuff
export Week='-D .calcurse/Weekly'
export Month='-D .calcurse/Monthly'
export Quarter='-D .calcurse/Quarterly'
export Year='-D .calcurse/Yearly'
I use tmux and a startup script to open daily, weekly, and monthly #!/bin/bash
# Start a session named cal, name the window "Day",
# pane. Detach the session for the setup process.
tmux new -s cal -n Day -d
# Create second window named "Week", split it and select left pane
tmux new-window -t cal:1 -n 'Week'
# Create a third window named "Month", split and select left
tmux new-window -t cal:2 -n 'Month'
# Load the calendars
## Note ^M and Enter seem to do the same thing
tmux send-keys -t cal:0 'calcurse' ^M
tmux send-keys -t cal:1 'calcurse $Week' ^M
tmux send-keys -t cal:2 'calcurse $Month' Enter
# Select window 0 and re-attach the session so we can reach it.
tmux select-window -t cal:0
tmux attach -t cal
Now I can set up tasks and priorities, and update according to the work plan. Share via rsyn. And not dependent on the cloud (I can rsync to a stick). Drawback; it is not integrated with Evolution or Thunderbird.Re: The Command-Line Office
#54Shameless plug for more terminal-based slide/presentation software: now with fading, 256 colour transitions and experimental PDF export! http://github.com/jclulow/vtmc
Very funny. :-)
Re: The Command-Line Office
#55Shameless plug for more terminal-based slide/presentation software: now with fading, 256 colour transitions and experimental PDF export! http://github.com/jclulow/vtmc
Re: The Command-Line Office
#56I'm a big command line fan, but vi/emac/nano are not word processors. They're text editors. You might be able to get close if you are using them to edit Markdown and running it through Pandoc (especially if you add in a non-commandline PDF viewer). But still. WordPerfect 5.1 - now that was a curses/command line word processor :) I don't know of a modern equivalent though.
Wordstar before then. It's a real shame that it is still legally encumbered, I'd love to use it on a modern system. http://en.wikipedia.org/wiki/Wordstar I actually found the other day I have a ROM for Wordwise+, the first word processor I ever used, for the BBC Micro. I might see if I can get away with doing some "real work" in it :-) http://en.wikipedia.org/wiki/Wordwise
Re: The Command-Line Office
#57Re: The Command-Line Office
#58I'm a big command line fan, but vi/emac/nano are not word processors. They're text editors. You might be able to get close if you are using them to edit Markdown and running it through Pandoc (especially if you add in a non-commandline PDF viewer). But still. WordPerfect 5.1 - now that was a curses/command line word processor :) I don't know of a modern equivalent though.
Many people would role their eyes at the idea of using a chain of console tools for document production, think of it as contrived. But it's not such a fancy idea. One of the first things to work on unix was roff, an ancestor of the man page system. It processed text documents into a printable form. Most serious document production company (publishing companies and newspapers; legal firms are probably less sophisticat…
LyX is already (mostly) there: http://lyx.org While it's mostly LaTeX based, I could easily see it using any number of backends (another feature of pipelining underneath), such as markdown, roff, etc.
Re: The Command-Line Office
#59Earlier quoted context omitted.
The unstated distinction you are making is between a program a novice can use for word processing and a program that requires some level of experience. I will grant that ed/edlin/nano are not word processors. But excluding emacs from the category is just as absurd as including ed. Have you used emacs in the past decade? Some of your requirements are laughable. Softwrapping? visual-line-mode has been baked in since 23…
Wait, can you style text in Emacs? Fonts? Colors? Bold, underline, italics? Isn't that the whole point of a word processor?