bittner / gedit-rest-plugin Goto Github PK

Hello,
I start gedit with the command :
| user@computer ~ $ gedit

When I want to generate a table, I have those lines in the terminal :
| Traceback (most recent call last):
| File "/usr/local/lib/gedit/plugins/reST/init.py", line 256, in on_create_table
| text = doc.get_text(start, end)
| TypeError: get_text() takes exactly 4 arguments (3 given)

Thank you for your work.

One bug that's still remaining is that the preview doesn't update when the text selection changes. It shouldn't be extremely difficult to fix, just finding the right signals to listen to, but I don't really see the point of this feature. When I select something it is usually to copy it. And 90% of the time a selection of a reST document won't be valid reST itself or is just a few words of plain text. Do you know the purpose/use case of this feature? If not, what about taking it out?

When I enable the plugin, it tries to work on ALL my files. Which is kind of unfortunate, because it tries to run reST processing even on my Python code etc., which obviously doesn't work well. I have suddenly tons of warning messages like:

<string>:75: (ERROR/3) Unexpected indentation.
<string>:79: (WARNING/2) Definition list ends without a blank line; unexpected unindent.
<string>:34: (ERROR/3) Unexpected indentation.
<string>:36: (WARNING/2) Definition list ends without a blank line; unexpected unindent.
<string>:37: (WARNING/2) Block quote ends without a blank line; unexpected unindent.

I know that gedit plugins are not the same as for example Emacs’ modes, so they natively are not limited just to some particular MIME type, but I guess with the heavy processes run by the plugin (e.g., whole WebKit and OpenJDK running) we should try to emulate this somehow with the infrastrcture we have.

If we moved most of the effective work to the Gedit.ViewActivatable child and cover whole processing with something like if filetype == 'reST': and ignore every other document. Of course, we would have to add also some event handler for case the user switches the file type of the edited document to reST (I guess we are talking about the file type used for the highlighting in gedit, MIME type is always just text/plain, right?).

There are a few files just lying around, which are effectively unused by the current implementation:

1. default.odt
2. default.sty
3. makeTable.py
4. to_html.py
5. to_odt.py
6. to_tex.py

Their original function is described in an older version of the README (and the french README in the doc folder).

@JanKanis Should we simply remove them to clean up the repository, or rather try to restore the features?

What do you think?

I am testing the plugin in Ubuntu 15.10/Gedit 3.18.2
I am currently stuck as there is no View/Bottom Panel entry available and cannot get the panel displayed

This is not really an issue, but: why the plugin is not part of standard gedit plugins? It would be far easier to use it in normal environments.
Thanks.

As suggested in PR #16, we should add a Preferences dialog to this plugin to allow user control over the behavior of the plugin.

Example Options

Code Examples

• Python Console
• Insert Date/Time
• rhythmbox-baidu-music

Table generation is broken due to import problems:

• ImportError: No module named 'makeTable'
• ImportError: No module named 'RegisterPygment'

Both in reST/__init__.py, lines 25+.

When referencing an image in gedit 3.14, there is just an empty box in the preview - the image is not displayed.

See an example on the screenshot
http://i58.tinypic.com/25qu4js.png

Plugins written for versions earlier than GEdit v3 aren't compatible with GEdit v3 anymore.

1. The .gedit-plugin file needs to be renamed to .plugin in order to be discovered by GEdit3 -- done
2. The GEdit API has changed; source code must be updated.

See the Wiki for development notes: https://github.com/bittner/gedit-reST-plugin/wiki/Development-Notes

I cannot get the plugin running on Debian x64 (Testing) with gedit 3.14

Here's the error message:
http://imgur.com/htAc538

Please contact me, if I can provide any additional information.

Problem Description

At the moment, when the reStructuredText Preview (Ctrl+Shift+R) is triggered and gedit's bottom panel is closed the reST document is generated, but the document is not displayed to the user. This is very irritating.

Proposed Solution

When the reStructuredText Preview (Ctrl+Shift+R) is triggered gedit should show the bottom panel (Ctrl+F9) if it is not visible yet.

I just installed this plugin on Gedit 3.10.4 (Ubuntu 14.04). When I activate it from the Preferences dialogue, I receive this error:

I tried to setup reST plugin on Fedora21.
python version available: Python 3.4.1

Steps followed :

clone source and switch to gedit-3.14 branch

https://github.com/bittner/gedit-reST-plugin.git

Install dependencies :

pygments:
pip install pygments

docutils: (http://docutils.sourceforge.net/README.html#installation)
git clone git://repo.or.cz/docutils.git
cd docutils/docutils ; python3 setup.py install

odtwriter : could not find the source for this.

copy reST.plugin and reST/ into the path for edit plugins in fedora21:

/usr/lib64/gedit/plugins

start gedit from terminal and load the plugin. I get the following error on terminal :

[saikrishna@localhost plugins]$ gedit
Traceback (most recent call last):
File "/usr/lib64/gedit/plugins/reST/init.py", line 22, in
from .restructuredtext import RestructuredtextHtmlPanel
File "/usr/lib64/gedit/plugins/reST/restructuredtext.py", line 20, in
from docutils.core import publish_parts
File "/usr/lib/python3.4/site-packages/docutils/init.py", line 68, in
class ApplicationError(StandardError):
NameError: name 'StandardError' is not defined

(gedit:12392): libpeas-WARNING **: Error loading plugin 'reST'

Please suggest.

hi

your plugin might have be usefull fo me if it works .
i can't active the plugin. when i tick it i get a red cercle. wherever i put the pyfile and its folder (user or global) the probleme is the same.

what's wrong?

distro: debian testing/gnome shell
gedit -v > 3.20

Hi, thanks for the plugin!

I'm trying it out to check if I can make it easier for people to write some documentation (written for Sphinx in rst)..
Looks promissing!

Opening one of the rst files I get an error about the 'toctree' Sphinx directive... :

If I'm right the issue here is that this is a sphinx directive and not a docutils directive?
Which is reasonable.
So I'm coining the idea here to have some list of directives to be ignored during parsing. So the plugin should "preflight" the text and remove the directives that are on that 'blacklist'.
Not sure if this is easy to do, or there are other ways to do this? Is there something like that in docutils maybe?

In the Preview-window one could either ignore it and show nothing, OR add some small message "ignored directive" or so?