public inbox for howm-eng@lists.osdn.me
 help / color / mirror / Atom feed
From: vukini at gmail.com (Vidyuth Kini)
Subject: [Howm-eng 99] Re: synchronizing howm notes over several computers
Date: Sat, 22 Sep 2012 14:55:04 +0400	[thread overview]
Message-ID: <0E294F35-CBD8-4703-867B-E3ED42E5F31B@gmail.com> (raw)
In-Reply-To: <86obkyigpr.fsf@willehalm.reiner>

Hi,

I found a solution that works pretty well for me. 

I changed the howm-directory variable in howm-vars.el to my shared network/cloud folder on Dropbox.

Then recompiled the file. 

Now I have howm synchronised on about 4 different machines and it works great.

if you don't have a network, simply sync the howm folder with all you data on it betwen machines I think would work. 

regards,

Vid



On Sep 22, 2012, at 12:50 PM, Albert Reiner <areiner at tph.tuwien.ac.at> wrote:

> Hello,
> 
> only recently did I start to use howm, and it seems that this will
> turn out a very valuable tool for me to use with just the right mix of
> functionality and simplicity - thanks a lot!
> 
> However, there are a few points that I am not so clear about, and my
> fluency in elisp is rather poor.  I am not quite sure whether this
> mailing list is still alive and the right place to ask questions about
> howm, so I will just try with the most pressing thing first:
> 
> - I need to be using howm on several different computers, without any
>  network connection between them most of the time.  Am I correct in
>  assuming that it is sufficient for me to simply synchronize the
>  various `howm-directory`s, and to copy any changes between the
>  accounts without relying on emacs/howm itself?  For this I would
>  probably use a revision control system, probably darcs.
> 
> - The thread on "Separating work and personal", and
>  <http://sourceforge.jp/projects/howm/lists/archive/eng/2008/000059.html>
>  in particular, make me suspect that I also have to take care of the
>  various `howm-keyword-file`s.  But the contents of
>  `howm-keyword-file` should actually be a function of the files
>  contained under howm-directory, so that it seems reasonable to me to
>  re-generate the keyword file afresh after pulling the changed notes.
>  As this should be little more than a `grep >>>`, this should not be
>  too slow (at least for now).
> 
>  So what is the easiest way to re-generate `howm-keyword-file`?  My
>  impression is that it should be sufficient to delete the file
>  whenever there are changes to it.
> 
> Thanks a lot in advance for any light you can shed on this question!
> 
> Albert.
> 
> _______________________________________________
> Howm-eng mailing list
> Howm-eng at lists.sourceforge.jp
> http://lists.sourceforge.jp/mailman/listinfo/howm-eng


  reply	other threads:[~2012-09-22 10:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-22  8:50 [Howm-eng 98] " areiner
2012-09-22 10:55 ` vukini [this message]
2012-09-23  9:42   ` [Howm-eng 100] " areiner
2012-09-23 11:51     ` [Howm-eng 101] " khi
2012-09-27  9:36       ` [Howm-eng 102] " areiner
2012-10-05 13:37         ` [Howm-eng 103] " khi
2012-10-08  7:19           ` [Howm-eng 104] " areiner
2012-10-09  9:17             ` [Howm-eng 105] " areiner
2012-12-27  3:31               ` [Howm-eng 111] " khi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0E294F35-CBD8-4703-867B-E3ED42E5F31B@gmail.com \
    --to=howm-eng@lists.osdn.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).