Shulou(Shulou.com)06/01 Report--

This article is about how to use Git to manage daily itinerary in linux. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Use Git to track your schedule

What if time itself is just source code that can be managed and versioned? While proving or refuting this theory may be beyond the scope of this article, with the help of Git, you can treat time as source code and manage your schedule.

The defending champion of calendars is the CalDAV protocol, which supports popular open source and closed source calendar applications such as NextCloud. There's nothing wrong with CalDAV (commentators, please note), but it's not for everyone, and beyond that, it has something inspiring that is different from a single culture.

Because I'm not interested in CalDAV clients that use a lot of GUI (if you're looking for a good terminal CalDAV viewer, see khal), I started working on text-based alternatives. Text-based calendars have all the common benefits of working in clear text. It's lightweight, very portable, and as long as it's structured, it's easy to analyze and beautify (no matter what beauty means to you).

Most importantly, it is exactly what Git aims to manage.

Org mode is not a scary way.

If you don't add structure to your plaintext, it will soon fall into a kind of wild chaos and become a symbol that only demons can understand. Fortunately, there is a markup syntax for calendars that is included in the respectable productivity Emacs pattern, the Org schema (admit it, you've always wanted to start using it).

Many people don't realize that the amazing thing about the Org pattern is that you don't need to know or even use Emacs to take advantage of the conventions established by the Org pattern. If you use Emacs, you'll get a lot of great features, but if Emacs is too difficult for you, you can implement a calendar system based on Git Org mode without having to install Emacs.

The only part you need to know about the Org pattern is its syntax. The syntax maintenance of Org mode is low-cost and intuitive. The biggest difference in using Org mode instead of the GUI calendar application for calendar recording is the workflow: you can create a task list and assign a task each day instead of going to the calendar and finding the date on which you want to schedule the task.

Lists in organizational mode use asterisks (*) as bullets. This is my game task list:

* Gaming** Build Stardrifter character** Read Stardrifter rules** Stardrifter playtest * * Blue Planet @ Mike's * * Run Rappan Athuk*** Purchase hard copy*** Skim Rappan Athuk*** Build Rappan Athuk maps in maptool*** Sort Rappan Athuk tokens

If you are familiar with CommonMark or Markdown, you will notice that the Org pattern does not use spaces to create subtasks, but uses other bullets more explicitly. Regardless of your background and list, this is an intuitive and easy way to build a list, and it obviously has nothing to do with Emacs (although using Emacs provides you with shortcuts, so you can quickly rearrange the list).

To convert the list to a scheduled task or event in your calendar, go back and add the keywords SCHEDULED and (optional): CATEGORY:.

* Gaming:CATEGORY: Game** Build Stardrifter characterSCHEDULED: * Read Stardrifter rulesSCHEDULED: * Stardrifter playtestSCHEDULED: * * Blue Planet @ Mike'sSCHEDULED: and so on...

The SCHEDULED keyword marks the entry as the event you want to be notified of, and optionally: the CATEGORY: keyword is an arbitrary marking system for your own use (in Emacs, you can use color codes for items according to category).

For repetitive events, you can use symbols (such as + 1w) to create weekly events or + 2w for biweekly events, and so on.

All the fancy tags available for Org mode are documented, so don't hesitate to find more tricks to make it meet your needs.

Put it into Git

Without Git, your Org mode schedule is just a file on your local computer. This is the 21st century, so you need to at least be able to use your calendar on your phone, even if not on all your personal computers. You can use Git to publish calendars for yourself and others.

First, create a directory for the. Org file. I store mine in ~ / cal.

$mkdir ~ / cal

Change to your directory and make it a Git repository:

$cd cal$ git init

Move the. Org file to your local Git repository. In practice, I maintain an. Org file for each category.

$mv ~ / * .org ~ / cal$ lsGame.org Meal.org Seth.org Work.org

Temporarily save and submit your documents:

$git add * .org$ git commit-m 'cal init' to create a Git remote source

To provide calendars anywhere, you must have a Git repository on the Internet. Your calendar is plain text, so any Git repository is fine. You can put your calendar on GitLab or any other public Git hosting service (or even a proprietary service), and you can even mark the repository as private as long as your host allows it. If you don't want to publish your calendar to a server you can't control, you can host your own Git repository, or use naked repositories for individual users, or use front-end services such as Gitolite or Gitea.

For simplicity, I will assume a self-hosted naked repository of Git. You can use the Git command to create a remote naked repository on any server with SSH access:

$ssh-p 22122 [seth@example.com] [14] [remote] $mkdir cal.git [remote] $cd cal.git [remote] $git init-- bare [remote] $exit

This naked repository can be used as your calendar's home on the Internet.

Set it as the remote source of the local Git repository (on your computer, not on your server):

$git remote add origin seth@example.com:/home/seth/cal.git

Then push your calendar to the server:

$git push-u origin HEAD

Put your calendar in the Git repository and you can use it on any device running Git. This means that you can update and change the plan and push the changes upstream so that they can be updated anywhere.

I use this method to keep my calendar synchronized between my work laptop and my home workstation. Since I spend most of my day using Emacs, it's a great convenience to be able to view and edit my calendar in Emacs. The same is true for most people who use mobile devices, so the next step is to set up a calendar system in Org mode on mobile devices.

Git on Mobile Devic

Because your calendar data is plain text, strictly speaking, you can "use" it on any device that can read text files. This is part of the beauty of the system; you will never be short of raw data. However, to integrate calendars into mobile devices the way you want modern calendars to work, you need two components: the Git client on the mobile device and the Org mode viewer.

Git client on mobile Devic

MGit is an excellent Git client on Android. Similarly, iOS also has a Git client.

Once MGit (or similar Git client) is installed, you must clone the calendar repository so that you can have a copy on your phone. To access the server from a mobile device, a SSH key must be set for authentication. MGit can generate and store keys for you, and you must add them to the server's ~ /. Ssh/authorized_keys file or to the SSH key in the account settings of the hosted Git.

You must do this manually. MGit does not have an interface to log in to your server or hosted Git account. If you don't, your mobile device will not be able to access your server to access your calendar data.

I did this by copying the key file I generated in MGit to my laptop via KDE Connect (but you can do the same via Bluetooth, SD card reader, or USB cable, depending on your preferred method of accessing data on your phone). I used this command to copy the key (a file named calkey) to my server:

$cat calkey | ssh seth@example.com "cat > > / home/seth/.ssh/authorized_keys"

You may have different methods, but if you have ever set the server to log in without a password, this is exactly the same process. If you are using a hosted Git service such as GitLab, you must copy and paste the contents of the key file into the SSH key panel of the user account.

Adding key file data to GitLab

When done, your mobile device can authorize your server, but you still need to know where to find your calendar data. Different applications may use different representations, but MGit uses plain old Git-over-SSH. This means that if you are using a non-standard SSH port, you must specify the SSH port to use:

$git clone ssh://seth@example.com:22122//home/seth/git/cal.git

Specifying SSH port in MGit

If you use another application, it may use a different syntax, allowing you to provide ports in special fields, or delete the ssh:// prefix. If you encounter problems, refer to the application documentation.

Clone the repository to the phone.

Cloned repositories

Few Git applications are set to update repositories automatically. There are some applications that can be used to pull automatically, or you can set Git hooks to push server updates-but I won't discuss them here. Currently, after updating the calendar, be sure to manually extract the new changes in MGit (or if you change the event on your phone, push the change to the server).

MGit push/pull settings

Calendars on mobile devices

There are some applications that can provide a front end for Org mode on mobile devices. Orgzly is a great open source Android application that provides an interface for most functions of the Org pattern, from Agenda mode to TODO lists. Install and start it.

From the main menu, select set synchronization Repository, and then select the directory that contains calendar files (that is, the Git repository cloned from the server).

Give Orgzly some time to import the data, and then use Orgzly's hamburger menu to select the calendar view.

Orgzly's agenda view

From the "set reminder" menu in Orgzly, you can choose the type of event that triggers the notification on your phone. You can get a SCHEDULED task, a DEADLINE task, or any notification of assigned event time. If you use your phone as a task manager, you will never miss Org mode and Orgzly activities.

Orgzly notification

Orgzly is more than just a parser. You can edit and update events, and even mark events as DONE.

Thank you for reading! This is the end of this article on "how to manage daily itinerary with Git in linux". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.