document/TranslateProject
2
0
Fork 0
mirror of https://github.com/LCTT/TranslateProject.git synced 2025-02-03 23:40:14 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #11317 from oneforalone/master

Browse Source 
translated by oneforalone
This commit is contained in:
Xingyu.Wang 2018-11-23 20:06:05 +08:00 committed by GitHub
commit 4cd239e3b9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 71 additions and 72 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

72
sources/tech/20180331 Emacs -4- Automated emails to org-mode and org-mode syncing.md
View File

@ -1,72 +0,0 @@
Emacs #4: Automated emails to org-mode and org-mode syncing
======
This is fourth in [a series on Emacs and org-mode][1].
Hopefully by now you’ve started to see how powerful and useful org-mode is. If you’re like me, you’re thinking:
“I’d really like to have this in sync across all my devices.”
and, perhaps:
“Can I forward emails into org-mode?”
This being Emacs, the answers, of course, are “Yes.”
### Syncing
Since org-mode just uses text files, syncing is pretty easily accomplished using any number of tools. I use git with git-remote-gcrypt. Due to some limitations of git-remote-gcrypt, each machine tends to push to its own branch, and to master on command. Each machine merges from all the other branches and pushes the result to master after a merge. A cron job causes pushes to the machine’s branch to happen, and a bit of elisp coordinates it all — making sure to save buffers before a sync, refresh them from disk after, etc.
The code for this post is somewhat more extended, so I will be linking to it on github rather than posting inline.
I have a directory $HOME/org where all my org-stuff lives. In ~/org lives [a Makefile][2] that handles the syncing. It defines these targets:
* push: adds, commits, and pushes to a branch named after the machine’s hostname
* fetch: does a simple git fetch
* sync: adds, commits, pulls remote changes, merges, and (assuming the merge was successful) pushes to the branch named after the machine’s hostname plus master
Now, in my user’s crontab, I have this:
```
*/15 * * * * make -C $HOME/org push fetch 2>&1 | logger --tag 'orgsync'
```
The [accompanying elisp code][3] defines a shortcut (C-c s) to cause a sync to occur. Thanks to the cronjob, as long as files were saved — even if I didn’t explicitly sync on the other boxen — they’ll be pulled in.
I have found this setup to work really well.
### Emailing to org-mode
Before going down this path, one should ask the question: do you really need it? I use org-mode with mu4e, and the integration is excellent; any org task can link to an email by message-id, and this is ideal — it lets a person do things like make a reminder to reply to a message in a week.
However, org is not just about reminders. It’s also a knowledge base, authoring system, etc. And, not all of my mail clients use mu4e. (Note: things like MobileOrg exist for mobile devices). I don’t actually use this as much as I thought I would, but it has its uses and I thought I’d document it here too.
Now I didn’t want to just be able to accept plain text email. I wanted to be able to handle attachments, HTML mail, etc. This quickly starts to sound problematic — but with tools like ripmime and pandoc, it’s not too bad.
The first step is to set up some way to get mail into a specific folder. A plus-extension, special user, whatever. I then use a [fetchmail configuration][4] to pull it down and run my [insorgmail][5] script.
This script is where all the interesting bits happen. It starts with ripmime to process the message. HTML bits are converted from HTML to org format using pandoc. an org hierarchy is made to represent the structure of the email as best as possible. emails can get pretty complicated, with HTML and the rest, but I have found this does an acceptable job with my use cases.
### Up next…
My last post on org-mode will talk about using it to write documents and prepare slides — a use for which I found myself surprisingly pleased with it, but which needed a bit of tweaking.
--------------------------------------------------------------------------------
via: http://changelog.complete.org/archives/9898-emacs-4-automated-emails-to-org-mode-and-org-mode-syncing
作者：[John Goerzen][a]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]:http://changelog.complete.org/
[1]:https://changelog.complete.org/archives/tag/emacs2018
[2]:https://github.com/jgoerzen/public-snippets/blob/master/emacs/org-tools/Makefile
[3]:https://github.com/jgoerzen/public-snippets/blob/master/emacs/org-tools/emacs-config.org
[4]:https://github.com/jgoerzen/public-snippets/blob/master/emacs/org-tools/fetchmailrc.orgmail
[5]:https://github.com/jgoerzen/public-snippets/blob/master/emacs/org-tools/insorgmail

71
translated/tech/20180331 Emacs -4- Automated emails to org-mode and org-mode syncing.md Normal file
View File

@ -0,0 +1,71 @@
Emacs #4：使用org-mode自动管理邮件及同步文档
======
这是 [Emacs 和 org-mode 系类][4]的第四篇。
至今为止，你已经见识到了 org-mode 的强大和高效，如果你像我一样，你可能会想：
“我真的很想让它在我所有的设备上同步。”
或者是说：
“我能在 org-mode 中转发邮件吗？”
答案当然是肯定的，因为这就是 Emacs。
### 同步
由于 org-mode 只使用文本文件，所以使用任意工具都可以很容易地实现同步。我使用的是 git 的 git-remote-gcrypt。由于 git-remote-gcrypt 的一些限制，每台机器都倾向于推到自己的分支，并使用命令来控制。每台机子都会先合并其他所有的 branch 然后再将合并后的结果 push 到 master 上。cron 作业可以实现将机器上的 branch push 上去，而 elisp 会协调这一切--确保在同步之前保存缓冲区，在同步之后从磁盘刷新缓冲区，等等。
这篇文章的代码有点多，所以我将把它链接到 github 上，而不是写在这里。
我有一个用来存放我所有的 org-stuff 的目录 $HOME/org，在 ~/org 目录下有个 [Makefile][2] 文件来处理同步。该文件定义了一下目标：
* push： 添加，提交和 push 到以主机命名的 branch 上
* fetch： 一个简单的 git fetch
* sync： 添加，提交和 pull 远程的修改，合并并将其 push 到以主机命名的 branch 和 master 上（假设合并成功）
现在，在我的用户 crontab 中有这个：
```
*/15 * * * * make -C $HOME/org push fetch 2>&1 | logger --tag 'orgsync'
```
[accompanying elisp code][3] 定义了一个快捷键（C-c s）来调用同步。多亏了 cronjob，只要文件被保存 -- 即使我没有在另一个 boxen 上同步 -- 它们也会被 pull 进来。
我发现这个设置非常好用。
### 用 org-mode 发邮件
在继续下去之前，首先要问自己一下：你真的需要它吗？ 我用的是带有 [mu4e][4] 的 org-mode，而且它集成的也很好；任何组织任务都可以通过 message-id 链接到电子邮件，这很理想 -- 它可以让一个人做一些事情，比如提醒他在一周内回复一条消息。
然而，org 不仅仅只有提醒。它还是一个知识库、创作系统等，但是并不是我所有的邮件客户端都使用 mu4e。(注意:像 MobileOrg 是存在于移动设备中)。我并没有像我想的那样经常使用它，但是它有它的用途，所以我认为我也应该在这里记录它。
现在我不仅想处理纯文本电子邮件。我希望能够处理附件、HTML 邮件等。这听起来很快就有问题了 -- 但是通过使用 ripmime 和 pandoc 这样的工具，情况还不错。
第一步就是要用某些方法将获取到的邮件放入指定的文件夹下。扩展名，特殊用户等。然后我用 [fetchmail configuration][5] 来将它 pull 下来并运行我自己的 [insorgmail][6] 脚本。
这个脚本就是处理所有有趣的部分了。它从 ripmime 开始处理消息，用 pandoc 将HTML 的部分转换为 org 格式。 org 的层次结构是用来尽可能最好地表示 email 的结构。使用HTML和其他工具时，email 可能会变得相当复杂，但我发现这对于我来说是可以接受的。
### 下一篇
我最后一篇关于 org-mode 的文章将讨论如何使用它来编写文档和准备幻灯片 -- 我发现自己对 org-mode 的使用非常满意，但这需要一些调整。
--------------------------------------------------------------------------------
via: http://changelog.complete.org/archives/9898-emacs-4-automated-emails-to-org-mode-and-org-mode-syncing
作者：[John Goerzen][a]
译者：[oneforalone](https://github.com/oneforalone)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]:http://changelog.complete.org/
[1]:https://changelog.complete.org/archives/tag/emacs2018
[2]:https://github.com/jgoerzen/public-snippets/blob/master/emacs/org-tools/Makefile
[3]:https://github.com/jgoerzen/public-snippets/blob/master/emacs/org-tools/emacs-config.org
[4]:https://www.emacswiki.org/emacs/mu4e
[5]:https://github.com/jgoerzen/public-snippets/blob/master/emacs/org-tools/fetchmailrc.orgmail
[6]:https://github.com/jgoerzen/public-snippets/blob/master/emacs/org-tools/insorgmail