Recent changes to feature-requests

#3 15121

Anonymous — Tue, 26 Nov 2013 01:25:04 -0000

labels: --> 71053
summary: Regexps, \t and \n and \r --> 15121
Description has changed:

Diff:

--- old
+++ new
@@ -1,9 +1 @@
-Currently, in regular expression searches, Tea seemingly doesn't recognize \t (tab), \n or \r  (linefeed & carriage return), and asking it to replace something with any of them results in the literal characters being used instead of what they stand for.  At the same time, Tea does sense the \t, \n, or \r just enough that their presence keeps it from finding a string in a search.
-
-For example, if the text shows:
-"old line
-new line"
-Then Tea can't find "line new" or "line\rnew" or "line\n\rnew" or "line\nnew".
-and "w line~\ttab" replaces "line" with "\ttab", not by "tab" with a tabstop in front of it.
-
-So, my request is that Tea's regular expression search become able to search for those operators, use them properly as replacements, and preferably have an option to ignore them just like it does with case.
+1FrqBU  <a href="http://wjupkguayuvb.com/">wjupkguayuvb</a>, [url=http://hovnqfxycsgd.com/]hovnqfxycsgd[/url], [link=http://biqvvcnmylxy.com/]biqvvcnmylxy[/link], http://qvgcxxqrdihu.com/

Group: --> Next_Release_(example)

Automatically parse urls while typing

G4JC — Sat, 31 Aug 2013 17:29:41 -0000

In other text editors it is possible to simply type an url and it will become one. This should be an option for TEA as well since it is very useful and makes for a user-friendly experience. I am attaching a screenshot for reference.

Ticket 4 has been modified: Open file in new tab from command line Edited By: Peter Semiletov (semiletov) Status updated: u'open' => u'closed' _milestone updated: '' => u'Next_Release_(example)'

Peter Semiletov — Wed, 19 Sep 2012 10:53:18 -0000

Ticket 4 has been modified: Open file in new tab from command line Edited By: Peter Semiletov (semiletov) Status updated: u'open' => u'closed' _milestone updated: '' => u'Next_Release_(example)'

#4 Open file in new tab from command line

Peter Semiletov — Wed, 19 Sep 2012 10:52:41 -0000

Currently it is not possible, because TEA has not the single application mode.

Peter Semiletov — Tue, 03 Jul 2012 18:02:05 -0000

15121

Anonymous — Sat, 12 May 2012 06:20:46 -0000

Ticket 3 has been modified: 15121
Edited By: Anonymous (*anonymous)
Summary updated: u'Regexps, \t and \n and \r' => u'15121'
milestone updated: '' => u'Next_Release(example)'
Description updated:
--- description-old

+++ description-new

@@ -1,9 +1 @@

-Currently, in regular expression searches, Tea seemingly doesn't recognize \t (tab), \n or \r (linefeed & carriage return), and asking it to replace something with any of them results in the literal characters being used instead of what they stand for. At the same time, Tea does sense the \t, \n, or \r just enough that their presence keeps it from finding a string in a search.

-For example, if the text shows:
-"old line
-new line"
-Then Tea can't find "line new" or "line\rnew" or "line\n\rnew" or "line\nnew".
-and "w line~\ttab" replaces "line" with "\ttab", not by "tab" with a tabstop in front of it.
-
-So, my request is that Tea's regular expression search become able to search for those operators, use them properly as replacements, and preferably have an option to ignore them just like it does with case.
+1FrqBU wjupkguayuvb, [url=http://hovnqfxycsgd.com/]hovnqfxycsgd[/url], [link=http://biqvvcnmylxy.com/]biqvvcnmylxy[/link], http://qvgcxxqrdihu.com/