Last modified: 2014-09-02 00:26:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T57059, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 55059 - Introducing "more" in replace.py
Introducing "more" in replace.py
Status: NEW
Product: Pywikibot
Classification: Unclassified
Other scripts (Other open bugs)
unspecified
All All
: Low enhancement
: ---
Assigned To: Pywikipedia bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-05 04:18 UTC by Kunal Mehta (Legoktm)
Modified: 2014-09-02 00:26 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Kunal Mehta (Legoktm) 2013-10-05 04:18:28 UTC
Originally from: http://sourceforge.net/p/pywikipediabot/feature-requests/260/
Reported by: binbot
Created on: 2010-08-24 09:32:57
Subject: Introducing "more" in replace.py
Original description:
In solve\_sisambiguation.py I can use "more" option to see a wider environment of the selected text. Repeating this, I see more and more of the text.
Would it be possible to implement this useful option in replace.py, too? Sometimes I need it very much, when the text is in a short line.
I can open the article in editor or browser, but it is too slow, and not always necessary. Pressing "m" as in solve\_sisambiguation.py would be much faster.
Comment 1 Ricordisamoa 2014-06-05 22:17:12 UTC
A similar system is also implemented in unlink.py and category.py. What about creating a centralized function for that?
Comment 2 wikiposta 2014-06-06 06:29:38 UTC
I am afraid it wouldn't be simple as the underlying displaying mechanisms are quite different. That's why I reported it and didn't solve yet.
As far as I remember, in case of replace.py replaceExcept from textlib.py does the modification and returns new text, then the caller calls showDiff to display portion of old and new text and asks the user to decide whether or not to change. Perhaps shoDiff should be avoked repeatedly with another parameter. Solve_disambiguatin has a displaying mechanism on its own, no showDiff.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links