This seems to work exactly as expected - thanks.Rickard Johansson wrote:It's been fixed. I'll release a new beta so please check when available.
Search found 83 matches
- 04 Sep 2011 16:16
- Forum: Syntax files
- Topic: FORTRAN keyword issues
- Replies: 6
- Views: 17201
Re: FORTRAN keyword issues
- 03 Sep 2011 15:14
- Forum: Scripts
- Topic: Running a program
- Replies: 1
- Views: 7202
Re: Running a program
While I'm not sure how to call an external program from a script, you could always write a DOS batch file that contains your commands and accepts appropriate arguments from the command line. Then, just define a custom tool in TextEd to call your batch file and pass the info needed. I think that woul...
- 01 Sep 2011 01:14
- Forum: External or integrated tools
- Topic: LINQPad - A versatile tool for .NET development
- Replies: 0
- Views: 11046
LINQPad - A versatile tool for .NET development
LINQPad's feature set is so diverse that it's difficult to describe. At its core, it's designed to allow rapid coding and testing of LINQ queries, but it does so much more... Including executing any C# or VB expression, statement, or entire program. It's a great tool for testing small (or large) ad-...
- 30 Aug 2011 23:40
- Forum: Syntax files
- Topic: FORTRAN keyword issues
- Replies: 6
- Views: 17201
Re: FORTRAN keyword issues
Will do - thank you.Rickard Johansson wrote:It's been fixed. I'll release a new beta so please check when available.
- 30 Aug 2011 15:42
- Forum: Syntax files
- Topic: FORTRAN keyword issues
- Replies: 6
- Views: 17201
Re: FORTRAN keyword issues
They all contain a "C" which is used as a line comment. It seems using an alphanumeric character as line comment can interfere with keyword identification. I'll look into it. That's an interesting observation, and I think you're right with one caveat. It only seems to impact the uppercase...
- 30 Aug 2011 01:09
- Forum: Syntax files
- Topic: FORTRAN keyword issues
- Replies: 6
- Views: 17201
Re: FORTRAN keyword issues
Rickard, I thought I'd go ahead and include the above word list and the syntax files for your review. Thanks, Jeff allocatable ALLOCATABLE allocate ALLOCATE backspace BACKSPACE deallocate DEALLOCATE equivalence EQUIVALENCE function FUNCTION implicit IMPLICIT include INCLUDE interface INTERFACE intri...
- 30 Aug 2011 00:42
- Forum: Syntax files
- Topic: FORTRAN keyword issues
- Replies: 6
- Views: 17201
FORTRAN keyword issues
Something odd is happening with my (very basic) FORTRAN syntax highlighter. All of my keywords are stored in the syntax file in lowercase, but the file is marked as not case sensitive. I've verified that *all* of the defined keywords are properly colorized when written in lower case. However, only *...
- 29 Aug 2011 23:54
- Forum: Syntax files
- Topic: FORTRAN syntax file
- Replies: 18
- Views: 38956
Re: FORTRAN syntax file
Sounds good - thanks!
Jeff
Jeff
- 29 Aug 2011 17:43
- Forum: Syntax files
- Topic: Another interesting syntax highlighting challenge
- Replies: 11
- Views: 25530
Re: Another interesting syntax highlighting challenge
Just tried this in 7.63 b2 and it's working great - thanks!Rickard Johansson wrote:I've made a small change in the draw function and it seems to be working now.
Jeff
- 29 Aug 2011 16:32
- Forum: Syntax files
- Topic: FORTRAN syntax file
- Replies: 18
- Views: 38956
Re: FORTRAN syntax file
I'll see if I can come up with something...but 5 different ways to make a line comment seems a bit much. An array of different values is probably the best solution e.g. =C|D|c|d|!|. As I said, it's not mission critical. However, it seems to me that a regex might be the *best* solution. In the case ...
- 29 Aug 2011 15:32
- Forum: Syntax files
- Topic: FORTRAN syntax file
- Replies: 18
- Views: 38956
Re: FORTRAN syntax file
Actually, I thought about that, but I don't think that was the case. Anyway, if you haven't seen my 2 previous responses, you might look at them.Rickard Johansson wrote:Seems you have an extra space after "C"
Thanks,
Jeff
- 29 Aug 2011 15:13
- Forum: Syntax files
- Topic: FORTRAN syntax file
- Replies: 18
- Views: 38956
Re: FORTRAN syntax file
In addition to the above response, Fortran is not case sensitive, and therefore the "C" comment character can be upper or lowercase. Currently, TextEd seems to only recognize a comment as defined (so, uppercase "C"). Maybe the comment parsing should leverage the CaseSensitive fla...
- 29 Aug 2011 15:07
- Forum: Syntax files
- Topic: FORTRAN syntax file
- Replies: 18
- Views: 38956
Re: FORTRAN syntax file
Wait... Now it's working! I seem to get tripped up by some kind of highlighting cache that I don't understand. I haven't yet found a guaranteed way to know that highlighter changes I just made are being reflected in the file I'm looking at (short of closing TextEd). Sometimes, the highlight seems to...
- 29 Aug 2011 14:53
- Forum: Syntax files
- Topic: FORTRAN syntax file
- Replies: 18
- Views: 38956
Re: FORTRAN syntax file
It seems to work on my end using LineCommentA=C OnlyLineCommentIfFirstCharA=2 Could you recheck? Hmmm... It doesn't seem to work here. Using this syntax definition: ;{} [Keywords] Keywords=allocatable|allocate|assign|backspace|block data|call|case|character|close|common|contains|continue|cycle|data...
- 29 Aug 2011 00:02
- Forum: Syntax files
- Topic: FORTRAN syntax file
- Replies: 18
- Views: 38956
Re: FORTRAN syntax file
The syntax option "OnlyLineCommentIfFirstChar" can now have 3 values in v7.63. OnlyLineCommentIfFirstChar=2 means the line comment start character has to be the first character on the line. Rickard, I just tried this, and it works (mostly) as expected. However, this doesn't work properly:...
