emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: dalanicolai <dalanicolai@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: contact management in emacs
Date: Sat, 27 Feb 2021 21:52:43 +0100	[thread overview]
Message-ID: <CACJP=3kbUAEUnKiRJ1Xa3p1ic0ad0n0JQYPh9WGD_hTYd78hLw@mail.gmail.com> (raw)
In-Reply-To: <mailman.47.1614445226.20994.emacs-orgmode@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 43245 bytes --]

I think all packages fulfill your requirements. So I would say it depends
on how many contacts you are managing. I have some experience with
org-contacts, and I find it very convenient and straightforward. It is also
very convenient to just use org-mode, i.e. a plain text file, for your
contacts. Every contact is a headline and you can add any kind of property
or tag etc. you want. Also anniversaries get added to the Agenda. You can
very easily jump to the right contact, using imenu or swoop/swiper (I use
`SPC j i ` in Spacemacs. So if you have less than say 300 contacts (I have
really no clue about the number of contacts that will still work smoothly),
then depending on how die-hard you are, I would recommend to start with
org-contacs. You can use org-vcard to import contacts, and org-vcard claims
to support exports too but I did not test that yet.
Anyway, I think you won't loose much time with setting up org-contacts and
from then you can slowly check out and study the other options.

I do not use Emacs for email yet, but org-contacts claims to support most
of Emacs its mail-readers.

If you enjoy tweaking your setup and study a little more then maybe
directly use BBDB or EBDB. EBDB's goal is to be a modern BBDB and I guess
the main developer does a very nice job. I have no experience with these
databases, because I think they are overkill (currently) for my usecase.

Daniel Nicolai

On Sat, 27 Feb 2021 at 18:03, <emacs-orgmode-request@gnu.org> wrote:

> Send Emacs-orgmode mailing list submissions to
>         emacs-orgmode@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.gnu.org/mailman/listinfo/emacs-orgmode
> or, via email, send a message with subject or body 'help' to
>         emacs-orgmode-request@gnu.org
>
> You can reach the person managing the list at
>         emacs-orgmode-owner@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Emacs-orgmode digest..."
>
>
> Today's Topics:
>
>    1. Re: Turning off all indentation in 9.4.4 (TRS-80)
>    2. Re: Tips on maintaining history in Org Mode (TRS-80)
>    3. Re: Set archive location relative to property (TRS-80)
>    4. [PATCH] ~org-font-lock-add-priority-faces~: ensure priority
>       cookies are in a headline (Sébastien Miquel)
>    5. Re: Tips on maintaining history in Org Mode (Samuel Wales)
>    6. Re: Tips on maintaining history in Org Mode (David Masterson)
>    7. Re: Tips on maintaining history in Org Mode (David Masterson)
>    8. Re: Tips on maintaining history in Org Mode (David Masterson)
>    9. Re: Tips on maintaining history in Org Mode (Tim Cross)
>   10. [bug] org-yank in stars corrupts outline (Samuel Wales)
>   11. Re: [bug] org-yank in stars corrupts outline (Samuel Wales)
>   12. Re: Tips on maintaining history in Org Mode (David Masterson)
>   13. Re: Tips on maintaining history in Org Mode (Samuel Wales)
>   14. Re: Tips on maintaining history in Org Mode (Ihor Radchenko)
>   15. Re: Tips on maintaining history in Org Mode (Ihor Radchenko)
>   16. Re: Tips on maintaining history in Org Mode (Ihor Radchenko)
>   17. contact management in emacs (Alan Schmitt)
>   18. Simple org-publish configuration example in manual does not
>       work (dalanicolai)
>   19. Re: contact management in emacs (Martin Steffen)
>   20. Re: [bug] org-yank in stars corrupts outline (Maxim Nikulin)
>   21. Re: [PATCH] org-mac-link: Disable Evernote capture by default
>       (Aaron Jensen)
>   22. Re: Babel: Programmatically evaluate a heading and subtrees?
>       (ian martins)
>   23. Re: contact management in emacs (andrés ramírez)
>   24. ob-reticulate: R+Python interface from Babel (Jack Kamm)
>   25. Re: contact management in emacs (Eric S Fraga)
>   26. Re: contact management in emacs (andrés ramírez)
>   27. Re: contact management in emacs (Martin Steffen)
>   28. Re: contact management in emacs (Bob Newell)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 26 Feb 2021 14:12:09 -0500
> From: TRS-80 <lists.trs-80@isnotmyreal.name>
> To: emacs-orgmode@gnu.org
> Subject: Re: Turning off all indentation in 9.4.4
> Message-ID: <83f49a373d71c4b786bda1ad6323ca87@isnotmyreal.name>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> On 2021-02-26 01:20, Kyle Meyer wrote:
> > TRS-80 writes:
> >
> >> On 2021-02-24 15:58, TRS-80 wrote:
> >>> On 2021-02-16 23:30, Kyle Meyer wrote:
> > [...]
> >>>> So, if I'm reading your preferences correctly, it sounds like you
> >>>> want
> >>>> just the first suggestion in the above snippet, leaving
> >>>> org-adapt-indentation at its default value:
> >>>>
> >>>>   (add-hook 'org-mode-hook (lambda () (electric-indent-local-mode
> >>>> -1)))
> >>>
> >>> OK, I just did eval-expression (M-:) with (electric-indent-local-mode
> >>> -1) in an Orgmode buffer.  After very brief testing, it does indeed
> >>> seem to return the desired behavior.  So thanks a lot for that tip!
> > [...]
> >> OK, so after that yesterday, I went ahead and added
> >> (electric-indent-local-mode -1) to my org-mode hook.  Then today upon
> >> re-starting Emacs, I am back to not working.
> >>
> >> By not working I mean:  Pressing enter goes to column 0 as it should,
> >> however then pressing <TAB> does nothing.  Where previously it would
> >> jump to same level as indented above.
> >>
> >> My settings are:
> >>
> >> - electric-indent-local-mode nil (local in each Orgmode buffer, set
> >> via
> >> hook)
> >>
> >> - org-adapt-indentation 'headline-data
> >
> > I'm just repeating my suggestion from above, but perhaps you want to
> > leave org-adapt-indentation at its default value of t?
>
> Apologies, I had skipped right over that bit!
>
> Doing as you say appears (after very brief test just now) to have given
> me back all the expected behavior:
>
> - RET goes to column zero
>
> - TAB goes to indentation level
>
> - Logbook entries are indented as they should be
>
> However in the course of doing this, it reminded me of what I was trying
> to do in the first place, which I thought I could accomplish with some
> of the new functionality (headline-data in particular).
>
> In my mind at least, the headline data belongs "with" the headline.  So
> all drawers like LOGBOOK and PROPERTIES (and their respective entries,
> of course) should all be indented to same level as headline.
>
> Now, I used to think the same way about the body text, but I changed my
> mind a year or two (maybe more) ago, as I realized that was just wasting
> too mych space.
>
> So, my reading of this new(?) headline-data setting, was that it seemed
> to be exactly what I had been looking for!  But perhaps I misunderstood?
>
> Cheers,
> TRS-80
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 26 Feb 2021 14:24:14 -0500
> From: TRS-80 <lists.trs-80@isnotmyreal.name>
> To: emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID: <45e4dc6434becb1552adc7df544db01a@isnotmyreal.name>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> On 2021-02-26 01:22, David Masterson wrote:
> > There are many ways of maintaining history in a group of Org files:
> > 1. Archive within a file
> > 2. Archive to a separate (archive) file
> > 3. Special TODO types for history
> > 4. Special TAG types for history
> > 5. etc.
> >
> > My question is, if you have meetings/phone calls as TODOs, what is the
> > preferred way to handle when they move into history so that, *much*
> > later, you can easily produce a list of all of the meetings/phone calls
> > with dates and times of them?  The issue (I think) is, when you mark
> > the
> > TODO as DONE, you lose the info of what the TODO was originally.
> >
> > Suggestions
>
> I agree with what others already said about logging state changes with
> timestamps.  I do the same and find this an extremely handy place to
> put "metadata about the task, or reason that it changed" and keep it
> separate/hidden from the main body of the task (which in my mind
> should only contain info about the subject of the headline / task
> itself).
>
> However when you say "history" I suspect you mean "archive" and this
> is something I have been thinking about a long time as well.  Because
> I think the current way that Orgmode handles this is a bit naive /
> simplistic.  Well, at least there is the option to create your own
> archival function, which I suspect I will do at some point.  In fact I
> have been thinking about the best way to do that for some time
> already.
>
> Cheers,
> TRS-80
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 26 Feb 2021 14:30:56 -0500
> From: TRS-80 <lists.trs-80@isnotmyreal.name>
> To: emacs-orgmode@gnu.org
> Subject: Re: Set archive location relative to property
> Message-ID: <565b3cb59087b33087676d8059a7e39d@isnotmyreal.name>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> On 2021-02-25 15:49, Florian Lindner wrote:
> > Am 25.02.21 um 21:22 schrieb Florian Lindner:
> >> is this possible with org-mode? Given a tree:
> >>
> >> * Name
> >> :PROPERTIES:
> >> :ARCHIVE:  ???
> >> :END:
> >> ** Archive    :ARCHIVE:
> >> ** Some node
> >>
> >> Upon archiving "Some node" (or any direct or indirect sub-node of
> >> Projectname) I want to end it up under "** Archive". The archive
> >> location should always be relative to the node where the property
> >> ARCHIVE is set.
> >>
> >> The documentation org-archive-location does not suggest that is
> >> possible.
> >
> > An alternative idea would be a setting for the ARCHIVE property that
> > searches the tree upward until it finds a node with an :ARCHIVE: tag
> > and use that as archive location. Maybe indicated by a setting of
> > "::%a".
> >
> > What do you think?
>
> I could be wrong, but my feeling (in either case) is something like
> that would probably require writing a custom archive function.
> Luckily, Orgmode allows you to do that.
>
> Cheers,
> TRS-80
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 26 Feb 2021 20:58:35 +0100
> From: Sébastien Miquel <sebastien.miquel@posteo.eu>
> To: emacs-orgmode@gnu.org
> Cc: Ihor Radchenko <yantar92@gmail.com>
> Subject: [PATCH] ~org-font-lock-add-priority-faces~: ensure priority
>         cookies are in a headline
> Message-ID: <a9f0fc01-2f32-8831-ac8b-0f0fe9e00a4d@posteo.eu>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Priority cookies are always in a headline.
>
> The attached patch speeds up fontification of a 1k lines buffer by 0.1
> second.
>
> Note that the variable org-priority-regexp can't be modified since
> it is used in the agenda and in org-get-priority.
>
> Regards,
>
> --
> Sébastien Miquel
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 0001-org.el-org-font-lock-add-priority-faces-Speed-up-reg.patch
> Type: text/x-patch
> Size: 967 bytes
> Desc: not available
> URL: <
> https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20210226/9ca34244/attachment.bin
> >
>
> ------------------------------
>
> Message: 5
> Date: Fri, 26 Feb 2021 14:34:43 -0700
> From: Samuel Wales <samologist@gmail.com>
> To: David Masterson <dsmasterson92630@outlook.com>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID:
>         <
> CAJcAo8uAc04c2v4xMhm8PWbp5v3wk3Jz13bDJDkdLFDnVs5kUw@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> org does indeed have a lot of related features, maybe too many even.
> here is some of what i do.
>
> - if i doneify, it means i will likely not need to search for it.
> archived to a file.
>   [currently the archiver is so slow i can't use it]
>   CLOSED: [2012-11-08 Thu 19:40]
> - state logging for repeaters in logbook
> - your question: notes to keep around like this
>   ***** LOG [2021-02-26 Fri 14:18] talked to bill gates; he uses linux now
>   these get sorted at bottom by timestamp using user-defined
>   this is the main thing
> - bare inactive free form as needed
>
> --
> The Kafka Pandemic
>
> Please learn what misopathy is.
>
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 26 Feb 2021 14:51:30 -0800
> From: David Masterson <dsmasterson92630@outlook.com>
> To: Ihor Radchenko <yantar92@gmail.com>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID:
>         <
> SJ0PR03MB5455FD17CD8FA3853983D5509B9D9@SJ0PR03MB5455.namprd03.prod.outlook.com
> >
>
> Content-Type: text/plain
>
> Ihor Radchenko <yantar92@gmail.com> writes:
>
> > David Masterson <dsmasterson92630@outlook.com> writes:
> >> My question is, if you have meetings/phone calls as TODOs, what is the
> >> preferred way to handle when they move into history so that, *much*
> >> later, you can easily produce a list of all of the meetings/phone calls
> >> with dates and times of them?  The issue (I think) is, when you mark the
> >> TODO as DONE, you lose the info of what the TODO was originally.
> >
> > See Org manual :: 5.3 Progress Logging
>
> Interesting, but then how do you get the list?  I mean is there an
> agenda to use?
> --
> David Masterson
>
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 26 Feb 2021 14:55:16 -0800
> From: David Masterson <dsmasterson92630@outlook.com>
> To: Tim Cross <theophilusx@gmail.com>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID:
>         <
> SJ0PR03MB5455A0B7779A6D32EDB6EC099B9D9@SJ0PR03MB5455.namprd03.prod.outlook.com
> >
>
> Content-Type: text/plain
>
> Tim Cross <theophilusx@gmail.com> writes:
>
> > David Masterson <dsmasterson92630@outlook.com> writes:
> >
> >> There are many ways of maintaining history in a group of Org files:
> >> 1. Archive within a file
> >> 2. Archive to a separate (archive) file
> >> 3. Special TODO types for history
> >> 4. Special TAG types for history
> >> 5. etc.
> >>
> >> My question is, if you have meetings/phone calls as TODOs, what is the
> >> preferred way to handle when they move into history so that, *much*
> >> later, you can easily produce a list of all of the meetings/phone calls
> >> with dates and times of them?  The issue (I think) is, when you mark the
> >> TODO as DONE, you lose the info of what the TODO was originally.
> >
> > A lot will depend on your requirements.
> >
> > For me, my TODOs are setup so that they record a date stamp for when
> > they were added and whenever they change state e.g. started, done,
> > delegated etc.
>
> So, you use progress logging.
>
> > For non-TODO items, I will often put an inactive timestamp in the
> > heading title.
>
> Do your headings become busy?
>
> What would you use to then make a list of all meetings you had last year?
>
> --
> David Masterson
>
>
>
> ------------------------------
>
> Message: 8
> Date: Fri, 26 Feb 2021 15:00:02 -0800
> From: David Masterson <dsmasterson92630@outlook.com>
> To: emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID:
>         <
> SJ0PR03MB54554F09F1784A4DE894233D9B9D9@SJ0PR03MB5455.namprd03.prod.outlook.com
> >
>
> Content-Type: text/plain
>
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
> > My approach is simple.  For TODO items, I archive to separate file when
> > done.  That file is easily searchable, e.g. using C-c /.
>
> Ah! org-occur! That's something forgot about and looks useful.
>
> > I keep both the original file and the archive file under revision
> > control, just in case.
>
> I do that, too.
>
> >> The issue (I think) is, when you mark the TODO as DONE, you lose the
> >> info of what the TODO was originally.
> >
> > What info is lost?  In fact, if you log state changes, all the
> > information is there.
>
> I see how that workss now with org-occur.
>
> > By the way, if you have recurring items, one package that you might find
> > useful is org-recur which is on ELPA.
>
> Thanks
>
> --
> David Masterson
>
>
>
> ------------------------------
>
> Message: 9
> Date: Sat, 27 Feb 2021 09:59:50 +1100
> From: Tim Cross <theophilusx@gmail.com>
> To: David Masterson <dsmasterson92630@outlook.com>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID: <87wnuu9zrf.fsf@gmail.com>
> Content-Type: text/plain
>
>
> David Masterson <dsmasterson92630@outlook.com> writes:
>
> > Tim Cross <theophilusx@gmail.com> writes:
> >
> >> David Masterson <dsmasterson92630@outlook.com> writes:
> >>
> >> For me, my TODOs are setup so that they record a date stamp for when
> >> they were added and whenever they change state e.g. started, done,
> >> delegated etc.
> >
> > So, you use progress logging.
>
> Yes.
>
> >
> >> For non-TODO items, I will often put an inactive timestamp in the
> >> heading title.
> >
> > Do your headings become busy?
> >
>
> Some would feel they are 'busy'. I always put the timestamp at the
> beginning of the heading, so there is a regular pattern (not much
> different from the leading heading stars) and I've just got use to it,
> so I don't really see it now.
>
> > What would you use to then make a list of all meetings you had last year?
>
> For me, archiving is about data I'm unlikely to need again, but just in
> case I do, it is in the archive. I rarely look at my archives. However,
> when I do archive, I will usually archive into a 'year' file. So, to
> find all the meetings held in 2015, I would open that archive file and
> search for entries with the tag MEETING (I also have a tag for PHONE).
>
> --
> Tim Cross
>
>
>
> ------------------------------
>
> Message: 10
> Date: Fri, 26 Feb 2021 17:52:37 -0700
> From: Samuel Wales <samologist@gmail.com>
> To: emacs-orgmode@gnu.org
> Subject: [bug] org-yank in stars corrupts outline
> Message-ID:
>         <CAJcAo8uF=
> JrtYWfe2HCPpgXcbD5kbGT78wtn67zXB8V_-SGWpg@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> it is neither raw yank behavior nor org syntax
>
> in recent maint
>
> i have org-yank-adjusted-subtrees t
>
> * org-yank is funny
> *** kill this line (with newline) then try yanking at ^ places (remove
> the ^ first)
> the fault lies in the stars
> insertion above and arbitrary demotion
> *** x
> asdfnaksdj fnkadsn fkjans df
> ^a^sdkfjnaksdfn kajsndfk ajdnsf
> askdjfkasjdn fkajfdns
> *^*^* y
> *** [[https://go^ogle.com]]
>
>
>
> ------------------------------
>
> Message: 11
> Date: Fri, 26 Feb 2021 17:54:36 -0700
> From: Samuel Wales <samologist@gmail.com>
> To: emacs-orgmode@gnu.org
> Subject: Re: [bug] org-yank in stars corrupts outline
> Message-ID:
>         <CAJcAo8vKRwzP_TAOwxCttC6o82O0g2OwOg_V+ep2E4=
> E3BxFxA@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> *** kill any header (with newline) then try yanking in various places
> in the stars of any indented header that has things above it.  you
> should get multiple demotions that do not conform to outline.
>
> On 2/26/21, Samuel Wales <samologist@gmail.com> wrote:
> > it is neither raw yank behavior nor org syntax
> >
> > in recent maint
> >
> > i have org-yank-adjusted-subtrees t
> >
> > * org-yank is funny
> > *** kill this line (with newline) then try yanking at ^ places (remove
> > the ^ first)
> > the fault lies in the stars
> > insertion above and arbitrary demotion
> > *** x
> > asdfnaksdj fnkadsn fkjans df
> > ^a^sdkfjnaksdfn kajsndfk ajdnsf
> > askdjfkasjdn fkajfdns
> > *^*^* y
> > *** [[https://go^ogle.com]]
> >
>
>
> --
> The Kafka Pandemic
>
> Please learn what misopathy is.
>
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>
>
>
> ------------------------------
>
> Message: 12
> Date: Fri, 26 Feb 2021 19:17:34 -0800
> From: David Masterson <dsmasterson92630@outlook.com>
> To: Tim Cross <theophilusx@gmail.com>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID:
>         <
> SJ0PR03MB5455951AD10B7FDB57BD87E39B9C9@SJ0PR03MB5455.namprd03.prod.outlook.com
> >
>
> Content-Type: text/plain
>
> Tim Cross <theophilusx@gmail.com> writes:
>
> > David Masterson <dsmasterson92630@outlook.com> writes:
> >
> >> What would you use to then make a list of all meetings you had last
> year?
> >
> > For me, archiving is about data I'm unlikely to need again, but just in
> > case I do, it is in the archive. I rarely look at my archives. However,
> > when I do archive, I will usually archive into a 'year' file. So, to
> > find all the meetings held in 2015, I would open that archive file and
> > search for entries with the tag MEETING (I also have a tag for PHONE).
>
> Got it.  Thanks.
> --
> David Masterson
>
>
>
> ------------------------------
>
> Message: 13
> Date: Fri, 26 Feb 2021 21:21:54 -0700
> From: Samuel Wales <samologist@gmail.com>
> To: David Masterson <dsmasterson92630@outlook.com>
> Cc: Tim Cross <theophilusx@gmail.com>, emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID:
>         <CAJcAo8tK7QiKLeBWe9+duQmntr2EER3pGXOJJy_Cx7vDu=
> djpg@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> note that there is an issue when you try to name your archive files
> using years like computer-2000.org_archive.  it can take seconds to
> find-file big files so it is understandable to want to name files like
> that.
>
> however, if you change the name of an archive file, it will not be
> found by org when you tell it to do certain things with archive files.
> some code in org derives the basename to search from the basename of
> the original file like computer,org.
>
> in principle, maybe org could allow year suffixes/prefixes or it could
> search all archive files in dirs that have org files.
>
> perhaps also changing org-archive-file-header-format to allow a format
> thingie for a timestamp would allow you to take parts of an archive
> file and move them into one per year without having to put the date in
> each archived entry.
>
>
> On 2/26/21, David Masterson <dsmasterson92630@outlook.com> wrote:
> > Tim Cross <theophilusx@gmail.com> writes:
> >
> >> David Masterson <dsmasterson92630@outlook.com> writes:
> >>
> >>> What would you use to then make a list of all meetings you had last
> >>> year?
> >>
> >> For me, archiving is about data I'm unlikely to need again, but just in
> >> case I do, it is in the archive. I rarely look at my archives. However,
> >> when I do archive, I will usually archive into a 'year' file. So, to
> >> find all the meetings held in 2015, I would open that archive file and
> >> search for entries with the tag MEETING (I also have a tag for PHONE).
> >
> > Got it.  Thanks.
> > --
> > David Masterson
> >
> >
>
>
> --
> The Kafka Pandemic
>
> Please learn what misopathy is.
>
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>
>
>
> ------------------------------
>
> Message: 14
> Date: Sat, 27 Feb 2021 14:28:13 +0800
> From: Ihor Radchenko <yantar92@gmail.com>
> To: David Masterson <dsmasterson92630@outlook.com>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID: <87czwmc9du.fsf@localhost>
> Content-Type: text/plain
>
> David Masterson <dsmasterson92630@outlook.com> writes:
>
> > Interesting, but then how do you get the list?  I mean is there an
> > agenda to use?
>
> Generally yes, you can use agenda. Or you can use sparse tree (more
> manual).
> For agenda, if you customise org-log-done, you can use
> org-agenda-log-mode ("v l" or "v L" in an agenda buffer). You can add
> archived items as well with "v a" or/and "v A".
>
> Just org-agenda-log-mode will show everything, not just calls. Narrowing
> to calls only will depend on how you define a todo, which is a call.
>
> If you use something like PHONE or CALL todo keywords, it might be
> slightly tricky. You will need to customise org-todo-keywords, so that
> your CALL->DONE changes are recorded (see the org-todo-keywords
> docstring). You will also need to filter displayed items in agenda by
> regexp involving the keyword you use to define the call.
>
> An easier way could be marking your calls with a tag. Then, you can
> filter your org-agenda-log by that tag to show only calls.
>
> Hope it helps.
>
> Best,
> Ihor
>
>
>
>
> ------------------------------
>
> Message: 15
> Date: Sat, 27 Feb 2021 14:38:47 +0800
> From: Ihor Radchenko <yantar92@gmail.com>
> To: Samuel Wales <samologist@gmail.com>, David Masterson
>         <dsmasterson92630@outlook.com>
> Cc: Tim Cross <theophilusx@gmail.com>, emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID: <87a6rqc8w8.fsf@localhost>
> Content-Type: text/plain
>
> Samuel Wales <samologist@gmail.com> writes:
>
> > perhaps also changing org-archive-file-header-format to allow a format
> > thingie for a timestamp would allow you to take parts of an archive
> > file and move them into one per year without having to put the date in
> > each archived entry.
>
> FYI: I have implemented automatic per-year archiving, which is correctly
> handled by other org commands in my personal config:
> https://github.com/yantar92/emacs-config/blob/master/config.org#archiving
>
> Best,
> Ihor
>
>
>
>
> ------------------------------
>
> Message: 16
> Date: Sat, 27 Feb 2021 14:42:03 +0800
> From: Ihor Radchenko <yantar92@gmail.com>
> To: Samuel Wales <samologist@gmail.com>, David Masterson
>         <dsmasterson92630@outlook.com>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: Tips on maintaining history in Org Mode
> Message-ID: <877dmuc8qs.fsf@localhost>
> Content-Type: text/plain
>
> Samuel Wales <samologist@gmail.com> writes:
> >   [currently the archiver is so slow i can't use it]
>
> Are your existing archives very big (few Mbs)? If so, you may try to
> speed up the archiving using feature/org-fold branch [1]. If that is not
> enough, I recommend splitting archives on yearly basis [2] or disabling
> font-lock in archive files.
>
> Best,
> Ihor
>
> [1] https://github.com/yantar92/org
> [2]
> https://github.com/yantar92/emacs-config/blob/master/config.org#archiving
>
>
>
>
> ------------------------------
>
> Message: 17
> Date: Sat, 27 Feb 2021 12:08:04 +0100
> From: Alan Schmitt <alan.schmitt@polytechnique.org>
> To: "emacs-orgmode" <emacs-orgmode@gnu.org>
> Subject: contact management in emacs
> Message-ID: <87lfb9bwff.fsf@m4x.org>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> This may be slightly off-topic for the list, but as I’m considering
> org-contacts for my question, I hope it will be of interest here.
>
> I would like to migrate my contact management to emacs, as I’m already
> using it for email. My requirements are the following ones:
> - address completion in emacs email clients (I currently use notmuch)
> - support for multiple email addresses and custom fields
> - creation of org links to contacts
> - export to vcard format for synchronization to my mobile phone (using
> vdirsyncer)
> - keep the data under version control
>
> I have looked at two tools, which almost seem fit for the job.
> - ebdb does most of this, with the exception of vcard export (it seems
> to be worked on, https://github.com/girzel/ebdb/issues/60), and I’m not
> sure using version control on an sqlite file is a good idea.
> - org-contacts also seem to have all the required features, including
> vcard export (and if not sufficient there is
> https://github.com/novoid/org-contacts2vcard). I was worried it was
> unmaintained when looking at the copyright line, but I see in
>
> https://code.orgmode.org/bzg/org-mode/commits/master/contrib/lisp/org-contacts.el
> that there are recent commits to the file.
>
> Do you manage your contacts in emacs? And if so, what tools or workflow
> do you recommend?
>
> Best,
>
> Alan
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 528 bytes
> Desc: not available
> URL: <
> https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20210227/1b6fa02c/attachment.sig
> >
>
> ------------------------------
>
> Message: 18
> Date: Sat, 27 Feb 2021 12:08:38 +0100
> From: dalanicolai <dalanicolai@gmail.com>
> To: emacs-orgmode@gnu.org
> Subject: Simple org-publish configuration example in manual does not
>         work
> Message-ID:
>         <CACJP=3k2jL1z0d-uALFGoutffFF2o=
> 7-L39zUns6si0KAhZ-_g@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello, sorry for sending this email directly, but currently sending mail
> from Emacs does not work correctly.
>
>
> I was trying out the org-publishing functionality, but I found that
> the first example in the documentation given at
> https://orgmode.org/manual/Simple-example.html#Simple-example
> does not work. When I try to publish the project it errors with the
> following message
>
> org-publish-file: No publishing function chosen
>
> So I figured that I should add a :publishing-function and I remembered
> reading earlier in the documnetation,
> i.e. at
> https://orgmode.org/manual/Publishing-action.html#Publishing-action
> org-html-publish-to-html
> <https://orgmode.org/manual/Publishing-action.html#Publishing-actionorg-html-publish-to-html>
> that org uses the default publishing-function
>
> org-publish-org-to-html
>
> But when trying to publish using that function then Emacs errors with
> the message
>
> org-publish-file: Symbol’s function definition is void:
> org-publish-org-to-html
>
> I have found the following error report from 17 Mar 2013, reporting
> exactly the same error (and a reply with the solution)
> https://lists.gnu.org/archive/html/emacs-orgmode/2013-03/msg01221.html
>
> It would be great if these two small point in the manual, which is
> otherwise great, could
> get updated.
>
> 1. add the required :publishing-function keyword to the documentation (with
> the correct function value)
> 2. change the name of the default function from org-publish-org-to-html ->
> *org-html-publish-to-html*
>
> Thank you!
>
> Best regards,
> Daniel Nicolai
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20210227/02a12cbf/attachment.html
> >
>
> ------------------------------
>
> Message: 19
> Date: Sat, 27 Feb 2021 12:31:05 +0100
> From: Martin Steffen <msteffen@ifi.uio.no>
> To: Alan Schmitt <alan.schmitt@polytechnique.org>
> Cc: emacs-orgmode <emacs-orgmode@gnu.org>
> Subject: Re: contact management in emacs
> Message-ID: <867dmteohy.fsf@login.ifi.uio.no>
> Content-Type: text/plain
>
>
>
>
> I use bbdb (big-brother data base). I use it since a looong time
> already, and amassed 15000 or so contracts. It does what I want, it's
> text-based, so versioning is not a problem.
>
> I think it can do vcard export (though when I used vcards is a long
> time ago, I can't remember if that was smooth, I think it was with one
> of my first smart phone, and I wanted to quick fill up the phone book
> there with my ``emacs-managed'' contact data base.).
>
> One can add used defined fields (where one can ``match'' all contacts
> for some criterion, and send then ``bulk'' email.
>
> Org is also bbdb-aware, insofar one can do those links: instead of
> [[file:xxxx][yyy]] one can use [[bbdb:somecriterion]].
>
> I don't know if it matches your needs, but I can't say bad things about
> that bbdb-thing.
>
> Martin
>
>
>
>
>
> ------------------------------
>
> Message: 20
> Date: Sat, 27 Feb 2021 18:55:54 +0700
> From: Maxim Nikulin <manikulin@gmail.com>
> To: emacs-orgmode@gnu.org
> Subject: Re: [bug] org-yank in stars corrupts outline
> Message-ID: <s1dc0b$udf$1@ciao.gmane.io>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 27/02/2021 07:52, Samuel Wales wrote:
> >
> > i have org-yank-adjusted-subtrees t
> >
> > * org-yank is funny
> > *** kill this line (with newline) then try yanking at ^ places (remove
> > the ^ first)
> > the fault lies in the stars
> > insertion above and arbitrary demotion
> > *** x
> > asdfnaksdj fnkadsn fkjans df
> > ^a^sdkfjnaksdfn kajsndfk ajdnsf
> > askdjfkasjdn fkajfdns
> > *^*^* y
> > *** [[https://go^ogle.com]]
>
> from [[help:org-yank]]
>
> > If it passes the test, and if the
> > cursor is at the beginning of a line or after the stars of a currently
> > empty headline, then the yank is handled specially.  How exactly depends
> > on the value of the following variables.
>
> In my opinion, your "^" marks do not satisfy the specified criteria.
>
> Personally I use [[help:org-paste-subtree]] C-c C-x C-y directly. It has
> a minor issue however. First time after emacs start it refuses to yank
> subtree from X clipboard (prepared externally). Regular paste with undo
> C-y C-/ is enough to convince the function that there is a subtree in
> the clipboard. Next time it works without such dance.
>
>
>
>
>
> ------------------------------
>
> Message: 21
> Date: Sat, 27 Feb 2021 07:14:52 -0600
> From: Aaron Jensen <aaronjensen@gmail.com>
> To: emacs-orgmode@gnu.org
> Subject: Re: [PATCH] org-mac-link: Disable Evernote capture by default
> Message-ID:
>         <CAHyO48x1rFo_CA_Ha3nZLNeWozurB=+
> 7pS1xOdc3p45nyF-y3Q@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Wed, Feb 17, 2021 at 9:55 AM Aaron Jensen <aaronjensen@gmail.com>
> wrote:
> >
> > The two `shell-command-to-string` invocations during eval are
> > extremely slow. Users of Evernote should `org-mac-grab-Evernote-app-p`
> > and `org-mac-evernote-path` explicitly.
>
> Hi all,
>
> Any chance of getting this merged in? It's a pretty nasty one for mac
> users.
>
> Thanks,
>
> Aaron
>
>
>
> ------------------------------
>
> Message: 22
> Date: Sat, 27 Feb 2021 08:18:45 -0500
> From: ian martins <ianxm@jhu.edu>
> To: Nathan Neff <nathan.neff@gmail.com>
> Cc: emacs-orgmode <emacs-orgmode@gnu.org>
> Subject: Re: Babel: Programmatically evaluate a heading and subtrees?
> Message-ID:
>         <CAC=rjb4iJPkXjOVAi83jjBrc=
> 4TjEZhr_KrEnYvF_K0GSapHOw@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Can you use noweb? In the example below, if you run the top code block
> babel will run the two that follow.
>
> A drawback is that you have to redefine variables, but it might be a
> benefit, since the individual blocks could be set with test data and
> the "main driver" could point to real data.
> -------
>
> #+begin_src elisp :results output :noweb yes :var data=data1
>   <<fun1>>
>   <<fun2>>
> #+end_src
>
> #+RESULTS:
> : called fun1: some data
> : called fun2
>
> #+name: data1
> some data
>
> #+name: fun1
> #+begin_src elisp :var data=data1
> (princ (format "called fun1: %s" data))
> #+end_src
>
> #+name: fun2
> #+begin_src elisp
> (princ "called fun2")
> #+end_src
>
> On Sat, Feb 20, 2021 at 2:11 PM Nathan Neff <nathan.neff@gmail.com> wrote:
> >
> > Hello all,
> >
> > I have some code like this:
> >
> > * Heading 1
> >
> > # code block name:FOO
> >
> > ** Subheading 1
> >
> > # code block
> >
> > ** Subheading 2
> >
> > # code block
> >
> > I find that I often want to evaluate the code in Heading 1 and its
> subheadings.
> >
> > Currently, I navigate to Heading 1 and then use org-babel-execute-subtree
> >
> > I see that there's a function called org-babel-goto-named-src-block, so
> I think
> > I could write a small function to jump to FOO in Heading 1 and then run
> execute subtree
> > and then jump back to my previous location in Emacs.
> >
> > Is there a more programmatic or built-in way?  For example:
> > org-babel-execute-block-and-subheadings FOO
> >
> > Thanks,
> > --Nate
>
>
>
> ------------------------------
>
> Message: 23
> Date: Sat, 27 Feb 2021 13:20:23 +0000
> From: andrés ramírez <rrandresf@gmail.com>
> To: Martin Steffen <msteffen@ifi.uio.no>
> Cc: Alan Schmitt <alan.schmitt@polytechnique.org>, emacs-orgmode
>         <emacs-orgmode@gnu.org>
> Subject: Re: contact management in emacs
> Message-ID: <868s79hcko.fsf@gmail.com>
> Content-Type: text/plain; charset=utf-8
>
> Hi. Martin and  Alan.
>
> >>>>> "Martin" == Martin Steffen <msteffen@ifi.uio.no> writes:
>
>
> [...]
>
>
>     Martin> Org is also bbdb-aware, insofar one can do those links:
> instead of [[file:xxxx][yyy]]
>     Martin> one can use [[bbdb:somecriterion]].
>
> bbdb anniversaries could also appear  on agenda:
> --8<---------------cut here---------------start------------->8---
> 10 days-agenda (W08-W09):
> Wednesday  24 February 2021
> Thursday   25 February 2021
> Friday     26 February 2021
> Saturday   27 February 2021
> Sunday     28 February 2021
> Monday      1 March 2021 W09
> Tuesday     2 March 2021
> Wednesday   3 March 2021
>   bbdb:       [[bbdb:Pedro ][Pedro  61st custom anniversary]]
> Thursday    4 March 2021
> Friday      5 March 2021
> --8<---------------cut here---------------end--------------->8---
>
> Andrés Ramírez
>
>
>
> ------------------------------
>
> Message: 24
> Date: Sat, 27 Feb 2021 06:15:29 -0800
> From: Jack Kamm <jackkamm@gmail.com>
> To: emacs-orgmode@gnu.org
> Subject: ob-reticulate: R+Python interface from Babel
> Message-ID: <87y2f94mwu.fsf@gmail.com>
> Content-Type: text/plain
>
> Hi all,
>
> ob-reticulate is now available on MELPA.
>
> You can find more information here:
> https://github.com/jackkamm/ob-reticulate
>
> Cheers,
> Jack
>
>
>
> ------------------------------
>
> Message: 25
> Date: Sat, 27 Feb 2021 14:40:32 +0000
> From: Eric S Fraga <e.fraga@ucl.ac.uk>
> To: andrés ramírez <rrandresf@gmail.com>
> Cc: emacs-orgmode <emacs-orgmode@gnu.org>
> Subject: Re: contact management in emacs
> Message-ID: <87lfb9y3of.fsf@ucl.ac.uk>
> Content-Type: text/plain; charset=utf-8
>
> On Saturday, 27 Feb 2021 at 13:20, andrés ramírez wrote:
> > bbdb anniversaries could also appear  on agenda:
>
> How do you get these to appear?  Or is the "could" a wish?
> thank you, eric
> --
> : Eric S Fraga via Emacs 28.0.50, Org release_9.4.4-231-gf46925
>
>
>
> ------------------------------
>
> Message: 26
> Date: Sat, 27 Feb 2021 15:12:00 +0000
> From: andrés ramírez <rrandresf@gmail.com>
> To: andrés ramírez <rrandresf@gmail.com>, emacs-orgmode
>         <emacs-orgmode@gnu.org>
> Subject: Re: contact management in emacs
> Message-ID: <868s79zgsf.fsf@gmail.com>
> Content-Type: text/plain
>
> Hi. Eric.
>
> >>>>> "Eric" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>
> [...]
>
>
>     Eric> How do you get these to appear?  Or is the "could" a wish?
>
> This is my setup:
> --8<---------------cut here---------------start------------->8---
> (setq org-agenda-files (directory-files "~/docs/org/deft/" t
> ".*agenda\.org$"))
> --8<---------------cut here---------------end--------------->8---
>
> ~/docs/org/deft/bbdb-anniversary-trick.agenda.org:
> --8<---------------cut here---------------start------------->8---
> * anniversary [isodate]
>   :PROPERTIES:
>   :CATEGORY: bbdb
>   :END:
> %%(when (fboundp 'my/org-bbdb-anniversaries) (my/org-bbdb-anniversaries))
> --8<---------------cut here---------------end--------------->8---
>
> --8<---------------cut here---------------start------------->8---
> (defun my/org-bbdb-anniversaries ()
> "It does not work on emacs-23"
>   (when (/= 23 emacs-major-version)
>     (org-bbdb-anniversaries)
>     )
>   )
>   --8<---------------cut here---------------end--------------->8---
>
> the bbdb record should have the field anniversary:
> --8<---------------cut here---------------start------------->8---
>         anniversary: 1960-03-03 custom
> --8<---------------cut here---------------end--------------->8---
>
> Best Regards
>
>
>
> ------------------------------
>
> Message: 27
> Date: Sat, 27 Feb 2021 16:14:19 +0100
> From: Martin Steffen <msteffen@ifi.uio.no>
> To: andrés ramírez <rrandresf@gmail.com>
> Cc: emacs-orgmode <emacs-orgmode@gnu.org>
> Subject: Re: contact management in emacs
> Message-ID: <8635xhee5w.fsf@login.ifi.uio.no>
> Content-Type: text/plain
>
> >>>>> "Eric" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>     Eric> How do you get these to appear?  Or is the "could" a wish?
>
> It's ``automatic''. The entry of the person needs a field "anniversary",
> if that's filled with a date in yyyy-mm-dd format, it's included
> (perhaps one has to set a variable like ``show-bbdb-anniversaries''
> and/or load a corresponding elisp-addition.)
>
>
> Martin
>
>
>
>
>     Eric> thank you, eric -- : Eric S Fraga via Emacs 28.0.50, Org
>     Eric> release_9.4.4-231-gf46925
>
>
>
>
> ------------------------------
>
> Message: 28
> Date: Sat, 27 Feb 2021 06:53:57 -1000
> From: Bob Newell <bobnewell@bobnewell.net>
> To: "emacs-orgmode" <emacs-orgmode@gnu.org>
> Subject: Re: contact management in emacs
> Message-ID: <s6jv9ad1mfu.fsf@emailmessageidheader.nil>
> Content-Type: text/plain
>
> I've used BBDB for years, and have tried org-contact, but it
> didn't seem to scale to the now rather large size of my BBDB
> database.
>
> I've looked at migrating to EBDB but as I have many custom
> functions I haven't yet made the move.
>
> BBDB can do amazing things. I've mentioned some of them
> before. Of course org links are supported, and in conjunction
> with the 'gnorb' package, Gnus email can be associated with
> BBDB entries in interesting ways.
>
> I use BBDB to easily maintain a slew of mailing lists. I also
> have custom functions to set the input language mode for those
> with whom I correspond in non-English languages. I even use
> BBDB to initiate phone calls when I'm on my desktop computer.
>
> I hadn't thought to put BBDB under version control but that
> would be very easy.
>
> However you don't need to get fancy right away. All the basics
> are there. Like many things Emacs, it does take time to get
> things set up the way you wish, but that time is well repaid
> down the road a little.
>
> --
> Bob Newell
> Honolulu, Hawai`i
>
> - Via GNU/Linux/Emacs/Gnus/BBDB
>
>
>
> End of Emacs-orgmode Digest, Vol 180, Issue 30
> **********************************************
>

[-- Attachment #2: Type: text/html, Size: 59355 bytes --]

  parent reply	other threads:[~2021-02-27 20:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.47.1614445226.20994.emacs-orgmode@gnu.org>
2021-02-27 18:57 ` content " Ian Garmaise
2021-02-27 19:16   ` Martin Steffen
2021-02-27 20:11     ` Juan Manuel Macías
2021-03-01  5:17     ` Bob Newell
2021-02-28 10:39   ` Eric S Fraga
2021-03-07 22:31   ` Jean Louis
2021-03-07 22:38   ` Jean Louis
2021-02-27 20:52 ` dalanicolai [this message]
2021-03-07 22:51   ` contact " Jean Louis
2021-02-27 11:08 Alan Schmitt
2021-02-27 11:31 ` Martin Steffen
2021-02-27 13:20   ` andrés ramírez
2021-02-27 14:40     ` Eric S Fraga
2021-02-27 15:12       ` andrés ramírez
2021-02-28 10:21         ` Eric S Fraga
2021-02-27 15:14       ` Martin Steffen
2021-02-27 17:00   ` Dr. Arne Babenhauserheide
2021-02-27 16:53 ` Bob Newell
2021-02-28  9:06 ` Russell Adams
2021-02-28 11:09   ` Alan Schmitt
2021-03-03 14:40   ` TRS-80
2021-03-07 22:57   ` Jean Louis
2021-03-08 20:06     ` John Kitchin
2021-03-10  8:32       ` Jean Louis
2021-03-07 22:13 ` Jean Louis
2021-03-08  7:49   ` Alan Schmitt
2021-03-08  8:12     ` Jose E. Marchesi
2021-03-10  8:32       ` Jean Louis

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to='CACJP=3kbUAEUnKiRJ1Xa3p1ic0ad0n0JQYPh9WGD_hTYd78hLw@mail.gmail.com' \
    --to=dalanicolai@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: contact management in emacs' \
    /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

Code repositories for project(s) associated with this inbox:

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).