brzydki | 1 May 13:00 2008
Picon

Check "Translations"


New polish translation was added.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

PCuff | 1 May 13:26 2008
Picon

eTrust Antivirus Detecting Virus in SciTE.exe


Hi everyone,

I'm using SciTE version 1.76 on Windows XP.

On my laptop at work this morning, I started getting the following
alert from our antivirus software (eTrust, v 7.1.501):
The Win32/Rewas!generic was detected in C:\SCITE\WSCITE\SCITE.EXE.

I googled Win32/Rewas!generic but couldn't find anything on it.

I have a desktop computer with SciTE and eTrust on it as well, but I'm
not getting the alert there. My laptop is using version 31.3750 of the
virus signature file (updated today), while the desktop is using
version 31.5749 (updated yesterday), so I'm guessing that this is
something new in the eTrust signatures, and that my desktop won't be
able to run SciTE either once the virus signature update is pushed to
it.

I can run SciTE.exe from a network share, or from my USB thumb drive
and the eTrust real time process monitor doesn't stop it from running.
When I try to copy SciTE.exe from the thumb drive to my laptop, eTrust
just deletes it.

Is SciTE.exe v1.76 truly infected with a virus, or is this a false
positive? Has anyone else had SciTE.exe flagged with a virus by eTrust
or any other antivirus software?

Thanks,

(Continue reading)

mozers | 1 May 15:08 2008
Picon

Re: eTrust Antivirus Detecting Virus in SciTE.exe


Thursday, May 1, 2008, 3:26:13 PM, PCuff wrote:

P> Is SciTE.exe v1.76 truly infected with a virus
P> alert from our antivirus software (eTrust, v 7.1.501):

Imho is this a false positive.
You can check up it on http://www.virustotal.com

--

-- 
mozers

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

PCuff | 1 May 15:58 2008
Picon

Re: eTrust Antivirus Detecting Virus in SciTE.exe


Thanks mozers :)

eTrust-Vet is the only scanner at VirusTotal that detects a virus. I
opened an issue with CA and asked them to verify that this file is
infected.

-- Pat

On May 1, 9:08 am, mozers <moz... <at> gmail.com> wrote:
> Thursday, May 1, 2008, 3:26:13 PM, PCuff wrote:
>
> P> Is SciTE.exe v1.76 truly infected with a virus
> P> alert from our antivirus software (eTrust, v 7.1.501):
>
> Imho is this a false positive.
> You can check up it onhttp://www.virustotal.com
>
> --
> mozers
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

Jeff | 2 May 07:38 2008
Picon

Re: "BS" in output window


I have a working solution the problem I was working on.  I added a
property called "interactive".  When it is set, any backspaces are
stripped (along with the previous char), from the buffer of characters
sent by an application to SciTE (before it is appended to the output
window).  The only code added is in SciTEWin::ExecuteOne and it only
impacts runtime when the "interactive" property is set.  Is there any
interest in this?  The diff is below.  If anyone knows a better way of
doing this, please let me know.

Thanks,
Jeff

$ diff SciTEWin_orig.cxx SciTEWin.cxx
646a647
>               bool interactive = props.GetInt("interactive", 0); // JSB added 20080411
722a724,735
>
>                                               if (interactive){
>                                                       int newLen = 0;
>                                                       for (int i = 0; i<bytesRead; i++){
>                                                               if (buffer[i]=='\b') {
>                                                                       if (newLen>0) newLen--;
>                                                                       else SendOutputEx(SCI_DELETEBACKNOTLINE,0,0,false);
>                                                               }       else buffer[newLen++]=buffer[i];
>                                                       }
>                                                       bytesRead = newLen;
>                                               }
>

(Continue reading)

PCuff | 2 May 13:00 2008
Picon

Re: eTrust Antivirus Detecting Virus in SciTE.exe


WHEW!

I've received a response from CA, and the SciTE.exe's been certified
clean. They updated their signature files to remove the false
positive. A quick update of my AV this morning and I'm back in
business :)

-- Pat

On May 1, 9:58 am, PCuff <patrick.c... <at> gmail.com> wrote:
> Thanks mozers :)
>
> eTrust-Vet is the only scanner at VirusTotal that detects a virus. I
> opened an issue with CA and asked them to verify that this file is
> infected.
>
> -- Pat
>
> On May 1, 9:08 am, mozers <moz... <at> gmail.com> wrote:
>
>
>
> > Thursday, May 1, 2008, 3:26:13 PM, PCuff wrote:
>
> > P> Is SciTE.exe v1.76 truly infected with a virus
> > P> alert from our antivirus software (eTrust, v 7.1.501):
>
> > Imho is this a false positive.
> > You can check up it onhttp://www.virustotal.com
(Continue reading)

Neil Hodgson | 4 May 05:18 2008
Picon

Re: Python indentation


From the comments:

 * 1.  If the lexer in use is for Python, automatically add one level of
 * indentation following a line which ends with a colon, after ignoring
 * whitespace and comments.  (This may require removal of any Python-
 * specific statement.indent instructions in properties files.)

   To be more widely usable, something like

block.start.when.last.$(file.patterns.py)=10 :
indent.comment.styles=0 1 12

   or extend the style number part of indentation properties to be
sets of styles:

block.start.if.last.$(file.patterns.py)=(5 10 11) :

   The set could include more styles but you are unlikely to have a
single line compound statement without a keyword or identifier after
the ':'.

 * 2.  When Enter is pressed, do not alter any preexisting indentation.
 * This affects all automatically indented languages, not just Python.

   If I have a compound C++ statement:
   if (c<z) { f(x); c++; }
   and then decide to make it take up multiple lines so place the
caret after the '{' and press Enter, I'd like the f(x) to go in the
right place rather than maintain the extra space.
(Continue reading)

John Yeung | 4 May 17:51 2008
Picon

Re: Python indentation


>    To be more widely usable, something like
>
> block.start.when.last.$(file.patterns.py)=10 :
> indent.comment.styles=0 1 12

I think I like this idea.  The main reason I didn't already do as you
describe is that my understanding of how to extract properties is very
sketchy.

>  * 2.  When Enter is pressed, do not alter any preexisting indentation.
>  * This affects all automatically indented languages, not just Python.
>
>    If I have a compound C++ statement:
>    if (c<z) { f(x); c++; }
>    and then decide to make it take up multiple lines so place the
> caret after the '{' and press Enter, I'd like the f(x) to go in the
> right place rather than maintain the extra space.

It goes in the right place.  My doc comment was not clear.  I should
have said something like:  "When Enter is pressed on a line which
isn't governed by properties-specified indentation rules, do not alter
preexisting indentation."

Essentially, I was trying to fix the indentation-destroying behavior
of the production version of SciTE, which I described (poorly) in
another thread ("Pressing Enter at beginning of line").  As such, my
implementation only differs from standard SciTE when you press Enter
while there is no text to the left of the caret.  That is, when the
caret is somewhere between column 1 and the leftmost text on the
(Continue reading)

Philippe Lhoste | 5 May 11:18 2008
Picon
Picon

Re: eTrust Antivirus Detecting Virus in SciTE.exe


On 02/05/2008 13:00, PCuff wrote:
> I've received a response from CA, and the SciTE.exe's been certified
> clean. They updated their signature files to remove the false
> positive. A quick update of my AV this morning and I'm back in
> business :)

Cool, good move. I saw this often with UPX compressed freewares... Some 
anti-virus seem to do more false positives of this kind...

--

-- 
Philippe Lhoste
--  (near) Paris -- France
--  http://Phi.Lho.free.fr
--  --  --  --  --  --  --  --  --  --  --  --  --  --

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

Neil Hodgson | 5 May 13:17 2008
Picon

Re: Python indentation


John Yeung:

>  > block.start.when.last.$(file.patterns.py)=10 :
>  > indent.comment.styles=0 1 12
>
>  I think I like this idea.  The main reason I didn't already do as you
>  describe is that my understanding of how to extract properties is very
>  sketchy.

   At the lowest level they just retrieve strings with variable
substitution. Then there are helpers for common cases like style
strings and the (style number with keywords) objects used for
indentation. I actually like the
"block.start.if.last.$(file.patterns.py)=(5 10 11) :" approach a
little more since parsing a more complex property format is simpler
(and may provide more capabilities) than coordinating a pair of
properties.

>  It goes in the right place.  My doc comment was not clear.  I should
>  have said something like:  "When Enter is pressed on a line which
>  isn't governed by properties-specified indentation rules, do not alter
>  preexisting indentation."

   Probably OK although there could be a property if it doesn't suit everyone.

>  There is.  The way I implemented change 2 requires indentation to be
>  added to restore the indentation to what it is supposed to be.  If the
>  end-of-line code is executed twice, too much indentation gets added.
>  There may be other ways to achieve the desired effect, but I couldn't
(Continue reading)


Gmane