From: Richard Riley <rileyrg@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-googlecl : enhancements - replace existing blog entries.
Date: Wed, 15 Sep 2010 18:27:41 +0200 [thread overview]
Message-ID: <i6qs5v$lcq$1@dough.gmane.org> (raw)
In-Reply-To: 87sk1bmisv.fsf@rochester.rr.com
Tim Burt <tcburt@rochester.rr.com> writes:
> Richard Riley <rileyrg@gmail.com> writes:
>
>> The org-googlecl package has been extended a little.
>>
>> http://splash-of-open-sauce.blogspot.com/2010/09/now-org-googlecl-supports-deleting-of_14.html
>>
>> It now detects if you try to blog an entry with the same title as an
>> existing one and prompts you to view and/or remove one or more entries
>> with the same name. Obviously very useful for just updating an entry (NB
>> the url will change unfortunately). There is also a footer option and
>> default labels (tags) if none are specified on the org entry you are
>> blogging.
>
> Tags as labels for the blog is a welcome feature.
You can now specify googlecl-blogged-tag : if set it will tag the org
entries that you blog. That tag wont be transmitted to the actual
blog. I'm wondering if a better idea is to log the url
of any new blog as a property of an org entry (option based of
course). Thoughts? it would mean you can instantly open your org entry
blog item and edit as you see fit.
In addition you can now set googlecl-auto-del to avoid delete
prompts - it will just automatically delete any entires with the same
title as your new blog.
cheers
r.
next prev parent reply other threads:[~2010-09-15 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 2:29 org-googlecl : enhancements - replace existing blog entries Richard Riley
2010-09-15 9:56 ` Tim Burt
2010-09-15 16:27 ` Richard Riley [this message]
2010-09-17 4:40 ` Richard Riley
2010-09-17 5:00 ` Richard Riley
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='i6qs5v$lcq$1@dough.gmane.org' \
--to=rileyrg@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public 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).