Opened on Dec 3, 2009 at 8:27:39 PM
Closed on Dec 29, 2009 at 9:16:15 PM
Last modified on Dec 29, 2009 at 9:18:33 PM
#1327 closed Bug (Fixed)
F1 in Scite Does Not Open Help File for Some Keywords
| Reported by: | wraithdu | Owned by: | Valik |
|---|---|---|---|
| Milestone: | 3.3.3.0 | Component: | Documentation |
| Version: | 3.3.1.6 | Severity: | None |
| Keywords: | F1 scite keyword | Cc: |
Description
For some keywords, the help file is not opened via F1 in Scite (with Scite4AutoIt3 installed). Examples of broken keywords:
Send
ConsoleWrite
StringRegExp
Attachments (0)
Change History (8)
comment:2 by , on Dec 8, 2009 at 8:17:55 PM
| Resolution: | → Works For Me |
|---|---|
| Status: | new → closed |
closed as there is no reply and cannot replicate the issue.
Jos
comment:3 by , on Dec 11, 2009 at 3:41:58 AM
Sorry, I forgot about this thread until today (no notifications of replies to trac tickets). Anyway, I fixed the problem, but I don't know why exactly. All I was doing was pressing F1 while the caret was within a keyword in Scite. I had to swap these two lines in au3.properties. Originally (the installation default) the command without quotes was active, and I had to swap it to activate the line with quotes.
Win7 Pro 32-bit
Scite 1.79
AutoIt 3.3.1.7
;command.help.$(au3)=$(autoit3dir)\Autoit3Help.exe $(CurrentWord) command.help.$(au3)=$(autoit3dir)\Autoit3Help.exe "$(CurrentWord)"
comment:4 by , on Dec 11, 2009 at 8:53:48 AM
| Resolution: | Works For Me |
|---|---|
| Status: | closed → reopened |
It actually would make more sense to me when we double-quote the command itself.
could you try that for me as i have no issues on my installation?
command.help.$(au3)="$(autoit3dir)\Autoit3Help.exe" $(CurrentWord)
Thanks
Jos
comment:5 by , on Dec 29, 2009 at 12:16:22 AM
Double quoting the command and not $(CurrentWord) exhibits the same odd behavior. Double quoting the command does not seem to make any difference as long as $(CurrentWord) is quoted. I guess some debugging of the Autoit3Help.exe helper app might be needed.
comment:6 by , on Dec 29, 2009 at 3:07:34 AM
I have already fixed some issues with that program that are probably related to your issue.
comment:7 by , on Dec 29, 2009 at 9:16:15 PM
| Milestone: | → 3.3.3.0 |
|---|---|
| Owner: | set to |
| Resolution: | → Fixed |
| Status: | reopened → closed |
Fixed by revision [5486] in version: 3.3.3.0
Works for me.
How did you test this?