Re: [O] Smart archiving of subtrees with parent headlines

2019-03-28 Thread Mark Edgington
May 1, 2018 at 11:01 AM Bastien wrote: > >> Hi Mark, >> >> Mark Edgington writes: >> >> > I don't know why not -- I'm OK with the code being used in >> > org-archive.el. As far as I'm concerned, you can use it however you >> > wish (it

Re: [O] Smart archiving of subtrees with parent headlines

2018-04-30 Thread Mark Edgington
Hi Bastien, On Thu, Apr 26, 2018 at 7:34 PM, Bastien wrote: > I'd be interested in integrating such a functionality in > org-archive.el. > > Do you think that is feasible? I don't know why not -- I'm OK with the code being used in org-archive.el. As far as I'm concerned, you can

Re: [O] FILETAGS tags hidden by TAGS option

2018-03-30 Thread Mark Edgington
Hi Nicolas, >> >> For example, with the following options, the foo tag will not show up >> when trying to do tab-completion, but only bar and baz will: >> >> #+TAGS: bar baz >> #+FILETAGS: foo > > FWIW, I cannot reproduce it (from master, I didn't check maint). You may > want to update Org and

[O] FILETAGS tags hidden by TAGS option

2018-03-28 Thread Mark Edgington
When using org-tags-view, the list of tags used for tab-completion fails to include tags specified via the #+FILETAGS option when there exists a #+TAGS option in the file which doesn't contain the #+FILETAGS tags. For example, with the following options, the foo tag will not show up when trying

Re: [O] Smart archiving of subtrees with parent headlines

2018-02-12 Thread Mark Edgington
While further evaluating my code, I realized that it wasn't working when target headlines contained tags. I've updated the code to handle this case -- the result is posted as a gist since it may change later on, and all of you esteemed elisp hackers can more easily contribute to it that way,

Re: [O] Smart archiving of subtrees with parent headlines

2018-02-12 Thread Mark Edgington
On Mon, Feb 12, 2018 at 1:54 AM, Ken Mankoff wrote: > > Does the attached file here work for you? I use it and it seems to do what > you describe. > > https://lists.gnu.org/archive/html/emacs-orgmode/2014-08/msg00109.html > Ken, I tried the code you included from your config

[O] CI for worg

2018-02-09 Thread Mark Edgington
Is there any kind of build-server connected with publishing org-mode documentation and/or the worg website? I ask because I have seen problems like the dead link here: https://orgmode.org/worg/org-contrib/babel/languages.html (which is referred to in

[O] Smart archiving of subtrees with parent headlines

2018-02-09 Thread Mark Edgington
Hello all, I have looked at a few threads related to the archiving of subtrees, but haven't found anything that matches what I think would be a very sensible archiving behavior. I already posted this as a question on the emacs stack-exchange site

Re: [O] Blank lines in LaTeX output due to org-mode comments

2016-06-30 Thread Mark Edgington
On Thu, Jun 30, 2016 at 5:23 PM, Nicolas Goaziou <m...@nicolasgoaziou.fr> wrote: > Mark Edgington <edgi...@gmail.com> writes: > >> I'm inclined to view it more as a bug, because it makes it impossible to >> place comments within a paragraph. > > This is

Re: [O] Need to update documentation to reflect export block syntax

2016-06-30 Thread Mark Edgington
Kaushal Modi gmail.com> writes: > Mark The online documentation corresponds to the stable releases of org-mode only. > The master branch is the dev branch. The only way to access the latest documentation is via the Info manual (M-x info in emacs to access that is the best way IMO). Thanks, I

Re: [O] Blank lines in LaTeX output due to org-mode comments

2016-06-30 Thread Mark Edgington
One other use case: when you want to comment out a single line in a paragraph, or have a few different lines within a paragraph that you wish to be able to select among by leaving only only one of them uncommented.

Re: [O] Blank lines in LaTeX output due to org-mode comments

2016-06-30 Thread Mark Edgington
Nicolas Goaziou nicolasgoaziou.fr> writes: > Mark Edgington gmail.com> writes: > > > Assume we have the following sample org-mode document: > > > > * Test Heading > > test test test test test test test > > test test test test test test test > &g

[O] Blank lines in LaTeX output due to org-mode comments

2016-06-30 Thread Mark Edgington
Assume we have the following sample org-mode document: * Test Heading test test test test test test test test test test test test test test test test test test test test test # HERE IS A COMMENT TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST

Re: [O] Need to update documentation to reflect export block syntax

2016-06-30 Thread Mark Edgington
It also might be worthwhile to have org-mode warn users (at least for a number of new releases) who happen to be using the old format, explaining that they need to use the new one to avoid problems when exporting.

[O] Need to update documentation to reflect export block syntax

2016-06-30 Thread Mark Edgington
I recently updated my org-mode git repository (for a long time I've had an older git version that I was using), and I am now having problems when doing latex exports. I bisected with git to find that the "problem" starts with this revision: commit 54318add34f09ff39d3fd034a4c1a89f60fd8759 Author:

Re: [O] org-export-with-broken-links doesn't apply to footnotes

2016-06-25 Thread Mark Edgington
Nicolas Goaziou nicolasgoaziou.fr> writes: > No, it isn't. However I could only reproduce it with empty footnote > definitions. > > In any case, this is now fixed. Thank you. I am providing a minimal example that still exhibits the problem for me (on the latest git rev): --- BEGIN

[O] org-export-with-broken-links doesn't apply to footnotes

2016-06-22 Thread Mark Edgington
The org-export-with-broken-links option was introduced in order to allow exports to proceed when a link isn't able to be resolved. Sometimes this happens when trying to export a narrowed region of a buffer. I have noticed, however, that even if I have (setq org-export-with-broken-links 't), I am

Re: [O] Restoring the org-freemind-to-org-mode function

2015-12-21 Thread Mark Edgington
On Dec 21, 2015 5:14 AM, "Vaidheeswaran C" < vaidheeswaran.chinnar...@gmail.com> wrote: > > Note: I would like to ensure that the file moves out of it's current > obscure place in contrib/lisp of Orgmode to a more visible place like > GNU ELPA before I expend any efforts on improving it. Why is

Re: [O] Restoring the org-freemind-to-org-mode function

2015-12-17 Thread Mark Edgington
On Dec 17, 2015 8:36 AM, "Nicolas Goaziou" wrote: > > org-freeming.el was replaced with ox-freeming.el, in contrib directory. > You may want to contact its author (which may not read this list) and > discuss if it would be possible to include the feature in that library >

[O] Restoring the org-freemind-to-org-mode function

2015-12-15 Thread Mark Edgington
I have in the past used the org-freemind-to-org-mode function, which is no longer included in org-mode. It used to be part of org-freemind.el file (see http://orgmode.org/w/org-mode.git?p=org-mode.git;a=blob_plain;f=lisp/org-freemind.el;hb=8f49547aaf0f9396f2a0bcfb25ce2c33be5e91fd ). I have since

[O] Comment lines interfere with figure options

2015-10-30 Thread Mark Edgington
If I have some org-mode content that looks like this... #+NAME: fig-myimage #+CAPTION: Caption of Figure #+ATTR_LaTeX: :width 5cm #+RESULTS: myimage [[file:images/myimage.png]] then I get a centered figure with the appropriate width and caption when exporting to LaTeX. If, however, I add a

Re: [O] org-collector unable to handle macros

2015-09-11 Thread Mark Edgington
Aaron Ecay gmail.com> writes: > > This looks like the same problem I reported (and provided a patch for) here: > . Some orgtbl-* > functions can’t cope with macro (or macro-resembling) text, because they > use the exporter, which expects

Re: [O] org-collector unable to handle macros

2015-09-08 Thread Mark Edgington
Nicolas Goaziou nicolasgoaziou.fr> writes: > > Mark Edgington gmail.com> writes: > > > On Aug 31, 2015 6:43 PM, "Nicolas Goaziou" nicolasgoaziou.fr> wrote: > >> > >> Hello, > >> > >> Mark Edgington gmail.com> writes: &

Re: [O] org-collector unable to handle macros

2015-08-31 Thread Mark Edgington
Charles Millar verizon.net> writes: > This may be related to the problem or is the same that I reported in > April and May and again earlier this month when Bastien's requested > details in his August 4th message. Have you (or anyone else) been able to reproduce the problem given the example

Re: [O] org-collector unable to handle macros

2015-08-31 Thread Mark Edgington
On Aug 31, 2015 6:43 PM, "Nicolas Goaziou" <m...@nicolasgoaziou.fr> wrote: > > Hello, > > Mark Edgington <edgi...@gmail.com> writes: > > > Charles Millar verizon.net> writes: > > > >> This may be related to the problem or is the

Re: [O] org-collector unable to handle macros

2015-08-31 Thread Mark Edgington
> >> > >> :INCLASS: ABC {{{c(stuff)}}} DEF > >> > >> looks incorrect. Macros are not expanded in node properties (with an > >> exception for :EXPORT_SOMETHING: when #+SOMETHING is parsed). > > > > It is not intended to be expanded when generating the table, but the table > > should have the

[O] org-collector unable to handle macros

2015-08-28 Thread Mark Edgington
I have had problems getting org-collector.el to generate tables where the content of the tables should include macros. At some point in the past this worked, but at this time (latest git version of org-mode), the following example fails (unless you remove the macro from the property definition):

[O] bad interaction between yasnippet and org-mode

2015-06-09 Thread Mark Edgington
I have a yas snippet that looks like the following: * $1 :sometag: $0 When I try to expand this snippet (on an empty line) in an org-mode buffer, there seems to be a bad interaction happening between org-mode and yasnippet, such that when entering in text at the $1 location,

[O] Bug: todo states not logged to drawer when using narrowed indirect buffer [8.3beta (release_8.3beta-1203-g93cc5f) ]

2015-06-04 Thread Mark Edgington
To reproduce this bug, do the following: 1. edit / open the following org file: #+TODO: TODO(t) WAIT(w!) | DONE(d!) CANCELED(c!) #+STARTUP: logdrawer * testing A some stuff * testing B 2. execute (org-tree-to-indirect-buffer) on the 'testing A' headline 3. go to the end

Re: [O] LaTeX_HEADER blocks

2015-05-27 Thread Mark Edgington
I noticed there was also a newer thread (around a year old) on this topic. It seems that what Nicolas Goaziou proposed earlier (about using #+attr_latex to modify whether a latex block is a header block or not) has not yet been implemented. This would be an alternative, though I find it more

[O] LaTeX_HEADER blocks

2015-05-27 Thread Mark Edgington
Hi Everyone, It is possible in org-mode to do either #+LaTeX: \somecommand or #+BEGIN_LaTeX \somecommand #+END_LaTeX I typically use the latter (the block form) because I often have multiple lines of LaTeX I would like to include at certain locations of a document. Similar to

Re: [O] math in footnotes not exported correctly when a buffer is narrowed

2015-05-19 Thread Mark Edgington
Rasmus rasmus at gmx.us writes: It was fixed a while ago in master. Are you using 8.2? Oh, I thought I was using something more recent, since the version was named 8.3beta, but apparently that's old. Thanks! A slight digression: I noticed, when cloning the git repo, that the current repo

[O] math in footnotes not exported correctly when a buffer is narrowed

2015-05-18 Thread Mark Edgington
I've noticed a bug in org-mode's LaTeX exporting of footnotes when a buffer is narrowed to a particular section. To reproduce, try to export the following org-file to a LaTeX document, and inspect the resulting LaTeX code -- it will have stripped the math environment off of \tau_s: * Test

[O] Babel blocks get unindented when making changes outside the blocks

2015-02-13 Thread Mark Edgington
Hello all, Given the following code: - BEGIN CODE - * some headline - blah - blah - blah - blah - blah #+begin_src octave first line if (num = 2) stuff end #+end_src - blah # some comments # more comments 1. item 1

[O] fontification of comment blocks (or any other kind of block)

2014-11-08 Thread Mark Edgington
It seems that there is nothing in place to allow the text inside blocks like: #+BEGIN_COMMENT ... #+END_COMMENT from having its face customized. It is possible to do this with quote and verse blocks, only not comment blocks. Would it be sensible to have a default block face which applies to

Re: [O] proposal to have ignoreheading tags/properties

2014-08-01 Thread Mark Edgington
filter, has flaws that cannot be fixed. Useful filters ought to be published in Worg, not included in core. Fair enough. Still, can someone add Eric's solution to contrib/lisp/ox-extra.el? Thanks, -- Bastien From 7b60eefcb21c2a62b1ab7f248f6a0b993d89cc4d Mon Sep 17 00:00:00 2001 From: Mark

Re: [O] proposal to have ignoreheading tags/properties

2014-07-28 Thread Mark Edgington
Hi Bastien, On Sun, Jul 27, 2014 at 1:21 PM, Bastien b...@gnu.org wrote: I suggest renaming ox-extra.el to ox-filters-extra.el and to have org-mode/lisp/ox-filters.el for filters that are important enough to be in core. Your suggestion sounds sensible, but of course I'm biased, as I've

Re: [O] proposal to have ignoreheading tags/properties

2014-07-28 Thread Mark Edgington
Hi Rasmus, Rasmus rasmus at gmx.us writes: Bastien bzg at gnu.org writes: I think Eric's filter is important enough to be in core, together with an option to let users decide what tag should be used instead of ignore (with ignore as a default). How about ignoreheading as this is

Re: [O] proposal to have ignoreheading tags/properties

2014-06-16 Thread Mark Edgington
Nicolas Goaziou mail at nicolasgoaziou.fr writes: Moreover, that task is highly specific; I'm not convinced we should have a dedicated keyword for each of them. I'd rather have a simple solution for selective export problems, even if, as a generic solution, it may look clumsier. Hi Nicolas,

Re: [O] proposal to have ignoreheading tags/properties

2014-06-14 Thread Mark Edgington
Nicolas Goaziou mail at nicolasgoaziou.fr writes: Actually, the problem is deeper than that. This :inline: tag is just a convoluted way to ask for a positive answer to another FAQ: « Can I close an outline section without starting a new section? »

[O] proposal to have ignoreheading tags/properties

2014-06-12 Thread Mark Edgington
In using org-mode, there is one problem that has always irked me (and is apparently also closely related to the FAQ How do I ignore a headline?). When I am writing something, I sometimes want to group things by concept or by work to be done, or any other number of groupings. BUT I do not want

Re: [O] proposal to have ignoreheading tags/properties

2014-06-12 Thread Mark Edgington
Thorsten Jolitz tjolitz at gmail.com writes: In a tree structure, when ignoring the parent node, it seems only logical that the siblings are ignored too. You seem to use the wrong tool for the task (headlines), this looks like a perfect use case for TAGS, i.e. define your (concept)

Re: [O] proposal to have ignoreheading tags/properties

2014-06-12 Thread Mark Edgington
Eric Schulte schulte.eric at gmail.com writes: Ken Mankoff mankoff at gmail.com writes: I don't think the word inline signifies that a heading will or won't be exported and/or its children promoted. Can you suggest a more intuitive/appropriate tag name? Would it be possible /

Re: [O] proposal to have ignoreheading tags/properties

2014-06-12 Thread Mark Edgington
Eric Abrahamsen eric at ericabrahamsen.net writes: It looks like a groundswell for remove-andor-promote tags for headlines, but for the sake of argument let me propose the use of blocks. It seems to me that something like a generic block (a block that does nothing but delete its begin/end

[O] bug in org-element-footnote-definition-parser?

2014-01-08 Thread Mark Edgington
I have encountered the following error message when trying to export to latex the attached example org file: org-element-footnote-definition-parser: Invalid search bound (wrong side of point) What is curious is that changing the number of 's in [fn:1] to 2 instead of 3 allows it to compile.

Re: [O] bug in org-element-footnote-definition-parser?

2014-01-08 Thread Mark Edgington
Nick Dokos ndokos at gmail.com writes: Nicolas Goaziou n.goaziou at gmail.com writes: Hello, Mark Edgington edgimar at gmail.com writes: I have encountered the following error message when trying to export to latex the attached example org file: org-element-footnote

Re: [O] TikZ (circuitikz) and org-preview-latex-fragment don't play nicely together

2013-12-11 Thread Mark Edgington
On Wed, Dec 11, 2013 at 3:46 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote: Mark Edgington edgi...@gmail.com writes: [...] Is there any way that I can make it so that without a lot of hacks I can make the previews appear as white-on-black, and the PDFs print black on white? Would something need

Re: [O] TikZ (circuitikz) and org-preview-latex-fragment don't play nicely together

2013-12-11 Thread Mark Edgington
Ok, I dug into the problem a little deeper, and it seems that it really can be considered a bug in the circuitikz code -- in order to remedy it for the present time, the circuitikz.code.tex file from this package should be modified, and the line: \ctikzset{color/.initial=black} must be removed /

Re: [O] TikZ (circuitikz) and org-preview-latex-fragment don't play nicely together

2013-12-11 Thread Mark Edgington
Nicolas Goaziou n.goaziou at gmail.com writes: You can remove offending packages with `org-export-before-parsing-hook' if you don't want them to be used during the export process. Yes, but I need the package which is buggy. If I were to remove it, I couldn't preview latex fragements or

[O] TikZ (circuitikz) and org-preview-latex-fragment don't play nicely together

2013-12-10 Thread Mark Edgington
Hello everyone, Assume I have an org-mode file that contains the following: -- #+OPTIONS: tex:imagemagick #+LaTeX_HEADER: \usepackage[siunitx]{circuitikz} * Test circuit #+begin_lateX \begin{circuitikz}[scale = 1.0] \draw (0,0) node[anchor=east]{$V_{in} -$}

[O] [PATCH] org-collector: enable specifying a default table-value as a parameter

2013-11-13 Thread Mark Edgington
Hi Bastien, Sorry about the formatting -- that's annoying. I've attached the patch. Here's its description: Currently there isn't an easy way to have default cell values which differ from one propview block to another. This patch enables one to specify what a cell's default value for a

[O] [PATCH] org-collector: enable specifying a default table-value as a parameter

2013-11-12 Thread Mark Edgington
Currently there isn't an easy way to have default cell values which differ from one propview block to another. This patch enables one to specify what a cell's default value for a block should be. For example, with this patch applied, you can do something like: #+BEGIN: propview :id

[O] Difference between LaTeX and HTML exported documents for bold verbatim text

2013-11-09 Thread Mark Edgington
Hello all, I have noticed that it if you have text like the following in org-mode: A *B* *=C=* then exporting to HTML causes A to be normal, B to be bold, and C to be bold and fixed-width font. Exporting the same to LaTeX, however, causes A to be normal, B to be bold, and C to be only

Re: [O] Difference between LaTeX and HTML exported documents for bold verbatim text

2013-11-09 Thread Mark Edgington
Aaron Ecay aaronecay at gmail.com writes: It would be nice if both exporters were consistent in how they export the styles for these cases (it seems like the HTML exporter gets it right, while the LaTeX exporter doesn't). This is an issue of the default font in LaTeX not providing the

Re: [O] Arbitrary lisp functions in column-attributes

2013-11-05 Thread Mark Edgington
Hi Bastien, On Tue, Nov 5, 2013 at 4:06 PM, Bastien b...@gnu.org wrote: One possible negative effect I can see is that users have to be extra careful what type of output such functions will produce, so that this output can be used by a summary type. Wouldn't the output of a function be

Re: [O] Arbitrary lisp functions in column-attributes

2013-11-04 Thread Mark Edgington
Bastien bzg at gnu.org writes: FWIW, I'd be inclined to say this is a bit *too much* -- but I'm curious to see if others have the same need. Hi Bastien, What about it seems too much? Or put differently, what do you think would be the negative effects of having something like this

Re: [O] Arbitrary lisp functions in column-attributes

2013-11-03 Thread Mark Edgington
How about using an elisp babel block, with tabular results? Something like (tested only very lightly): #+BEGIN_SRC elisp :results table (cons (list Header A Header B) (cons 'hline (org-map-entries (lambda () (list (princ

Re: [O] Org-Mode newbie, configuration?

2013-11-02 Thread Mark Edgington
Hi Joe, While it isn't org-mode specific, you might want to take a look at Eric Schulte's Emacs Starter Kit configuration (http://eschulte.github.io/emacs24-starter-kit/) -- it includes some org-mode settings, and is an example of a great way of maintaining your emacs configuration. Regards,

Re: [O] Arbitrary lisp functions in column-attributes

2013-11-01 Thread Mark Edgington
Hi Aaron, I hadn't actually foreseen using it for column-view so much, but rather for a dynamic-block which generates a column-view of a tree. These are, as far as I understand, read-only. I don't think it would work well with read-write column-views, so if such a function were defined in the

Re: [O] Arbitrary lisp functions in column-attributes

2013-10-31 Thread Mark Edgington
Hello all, Since the formatting on my earlier post was bad, I'm re-posting this with a bit more information: I would really appreciate it if it were possible to specify an arbitrary lisp function to process node-properties when creating a column view. Currently it is possible to have something

[O] Arbitrary lisp functions in column-attributes

2013-10-28 Thread Mark Edgington
Hello all, I would really appreciate it if it were possible to specify an arbitrary lisp function to process node-properties when creating a column view. For example, you can currently have something like: * Top node for columns view :PROPERTIES: :COLUMNS: %25ITEM %TAGS %PRIORITY %TODO

[O] org-babel generated images and +ATTR_LATEX

2013-10-23 Thread Mark Edgington
Hello all, I have noticed that it seems not possible to evaluate a babel block of code which generates an image, and to have a #+ATTR_LATEX line exist which immediately precedes the generated link to the image. In other words, If there's already a #+ATTR_LATEX line, I need to move it after the

Re: [O] org-babel generated images and +ATTR_LATEX

2013-10-23 Thread Mark Edgington
Hi Mike, That does help -- when testing it, I found that the problem had more to do with my header options than to do with the presence or absence of a #+NAME line. But still, with the header options I gave in my original example, org-babel's behavior does seem strange (maybe buggy?) to me. My

[O] Orgmode fails to export specific web-links as latex/pdf

2013-07-08 Thread Mark Edgington
Hello all- When trying to export via latex - pdf, the following org-mode snippet fails to compile. Presumably there's something that should be changed in the export filters? Here's the org-mode snippet: - ***

[O] Unable to use +LaTeX_HEADER: \input{...} with latex-preview-fragment

2013-06-04 Thread Mark Edgington
I attempted recently to have org-mode use a preamble file when previewing latex-fragments. I used a line like the following: +LaTeX_HEADER: \input{relative-path-to-file.tex} Unfortunately, the file referenced by the \input{} command doesn't get copied to the location where the preview tex

Re: [O] [PATCH] Export: Override headline numbering via properties

2013-05-13 Thread Mark Edgington
Hello Nicolas, I'm sorry for not having provided more explanation of the patch's purpose. The motivation is basically to permit any kind of manual (in contrast to automatic) control over the section-numbering behavior connected with a particular headline. In LaTeX, for example, you are able to

Re: [O] [PATCH] Export: Override headline numbering via properties

2013-05-13 Thread Mark Edgington
Hi Samuel, I'd guess it isn't exactly the same as what you did -- I assume you are making it possible to modify the numbering level threshold via properties. Is this modification inherited by child-headlines or not? Either way, there would be a lot of hackery required to use this to achieve the

Re: [O] [PATCH] Export: Override headline numbering via properties

2013-05-13 Thread Mark Edgington
Also, I forgot to mention that the patch is tested, and behaves as expected. On Mon, May 13, 2013 at 2:18 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: Thanks for your patch. Though, I don't get what you are trying to achieve nor what a use case would be. Have you tested this patch ? It may

Re: [O] [PATCH] Export: Override headline numbering via properties

2013-05-13 Thread Mark Edgington
Hi Nicolas, On Mon, May 13, 2013 at 6:54 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: You can still number these parts manually with, e.g., #+latex: \section*{Introduction} before the first section in your Org document. While this is possible, wouldn't this break the structure of the

[O] [PATCH] Export: Override headline numbering via properties

2013-05-12 Thread Mark Edgington
* lisp/ox.el (org-export-numbered-headline-p): If the `:NUMBERED' property is defined for a headline, turn numbering on when the property value is y (otherwise turn numbering off). Do the same if the `:INHERITED_NUMBERED' property is defined for a headline, except make this property inherited by

[O] keymap for read-date-minibuffer

2013-01-24 Thread Mark Edgington
Hello all, I recently spent a while figuring out how to add custom-keybindings to the read-date-minibuffer which appears when org-read-date is called. The only way to do it currently is to use the org-read-date-minibuffer-setup hook, and add keybindings to the minibuffer-local-map there. I'm

[O] Announcing a script that connects org-mode and google-tasks

2012-10-26 Thread Mark Edgington
Hello all- I hacked together a python script based on some already-existing code, which allows one to push an org file to a google-tasks list, or to pull the contents of a google-tasks list into an org file. Though the code isn't beautiful at the moment, it is functional. Feel free to improve