editor=stdin

[GoogleCodeExporter]

===NOTE===
If you're asking for a new service that isn't supported by gdata-python-
client, this will immediately get flagged as WontFix.
==========

What service (Calendar, Docs, Picasa) should be enhanced?
Docs
What is the enhancement?
editor = stdin 

google docs edit --title "sometitle" --editor=stdin --format=csv << 
sometitle.csv 

Original issue reported on code.google.com by brandonn...@gmail.com on 23 Aug 2010 at 8:27

[GoogleCodeExporter]

This is fixed in r530. Issue 104 and Issue 340 were already closed by that.

Original comment by livibet...@gmail.com on 14 Aug 2011 at 6:12

[GoogleCodeExporter]

This has not been fixed. Why was this closed. You still can't edit the doc from 
the cli. only upload. 

Original comment by brandonn...@gmail.com on 26 Aug 2011 at 11:38

[GoogleCodeExporter]

I apologize for giving you wrong info. This is not closed, I am not a project 
member, can't do that.

I thought docs also supported stdin by using

  google docs edit --title _ < filename

Original comment by livibet...@gmail.com on 26 Aug 2011 at 12:30

[GoogleCodeExporter]

A patch for uploading and editing using stdin is attached.

When upload, you use the following syntax to specify for using stdin as src

  _.<ext>

The <ext> is the file type, it’s required. It’s just like normal file 
extensions, e.g. you can use

  _.txt
  _.odt
  [... and so on}

When edit, you specify the editor is _, e.g.

  --editor _ < file_to_use

Example commands for upload and edit:

  ./google.py docs upload --title ’testdoc’ _.odt < test.odt
  ./google.py docs edit --title ’testdoc’ --format odt --editor _ < test.odt

(Note that --format option is important for .odt (and maybe other types), or 
you might get a text format to edit)

If there is real need for filename such as _.odt, then you should type in as 
./_.odt or use full/relative path.

Original comment by livibet...@gmail.com on 27 Aug 2011 at 8:15

Attachments:

• docs-stdin-upload-edit.r561.patch