Re: [gedit-list] "Fixing" long line indentation (aka smart indent)

[Timothy Arceri <t_arceri yahoo com au>]

I'm not sure what distro you are using but Ubuntu has a project called One Hundred Papercuts where small usability issues are targeted for a selected group of apps. This release cycle Gedit is being targeted so I have added this bug you have pointed out. With any luck it might get some attention.

https://launchpad.net/hundredpapercuts/+milestone/gedit

Cheers,

Tim

---

From: "gedit-list-request gnome org" <gedit-list-request gnome org>
To: gedi

Message: 1
Date: Mon, 03 Dec 2012 17:06:40 -0500
From: Matt Chaput <matt sidefx com>
To: gedit-list gnome org
Subject: [gedit-list] "Fixing" long line indentation (aka smart
    indent)
Message-ID: <50BD2270 3080402 sidefx com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi gedit mailing list,

I work at Side Effects Software in the documentation department. Side
Effects Software makes Houdini, a very advanced 3D animation and effects
package used in most films made today, as well as in games and commercials.

We use a custom-built wiki markup/parser to write the documentation. We
need a text editor with the ability to easily specify a custom syntax
coloring for our markup, as well as modern GUI conveniences that
non-technical people expect. Currently we're using a somewhat obscure
Windows-only editor called EditPad Pro, but we're trying to switch to
something better.

I've evaluated SublimeText 2, Komodo Edit, GEdit, and Kate. Gedit scores
extremely well on our criteria, with one deal-breaker: lack of soft-wrap
with smart indent (by which I mean that wrapped "virtual" lines should
retain the visual indentation of the "real" line):

  https://bugzilla.gnome.org/show_bug.cgi?id=559132

This is basically the only thing preventing me from pulling the trigger
on switching our company to using gedit for docs (and telling our
customers such as Pixar, ILM, and Dreamworks to use gedit to edit the
docs for their custom Houdini assets).

So, I'm motivated to try to get this fixed. I as a lowly technical
writer probably can't get the company to pay to have this fixed.
However, I might be able to have one of our co-ops tasked with fixing
this if we could find a GTK/gedit dev to mentor them. Or, I could trade
work on the gedit documentation for gedit devs fixing this directly.

Any ideas on where I should go from here? Any sense of how much work
this would be to fix? Anyone thinking of working on this that I can
convince/motivate/bribe to get started?

Thanks,

Matt Chaput
Side Effects Software documentation

tl;dr: I'd like to work with the gedit devs to try to get this fixed:
https://bugzilla.gnome.org/show_bug.cgi?id=559132




------------------------------

_______________________________________________
gedit-list mailing list
gedit-list gnome org
https://mail.gnome.org/mailman/listinfo/gedit-list


End of gedit-list Digest, Vol 95, Issue 1
*****************************************