R and Scite-Mac OSX

[Chris]

Hi,
I recently purchased Scite-Mac OSX to use with R. But to my chagrin
there was no R syntax file enabled by default. I believe I can enable
this. After a little googling, I found that if I enable R||R||\ in
SciteGlobal.Properties that this might do it. However, apparently I
can't save that file after making changes to it?

Any help would be greatly appreciated. I am completely new to Scite
and want to use it for R and LaTeX. Also, does anyone know if you get
free upgrades for Scite-Mac OSX?

Chris

[Christopher David Desjardins]

Update,
So I figured out how to enable the R language file by adding it to SciteUser.properties. Here is what I've done. Someone more expect than me please let me know if there is a better way. Also it seems that it doesn't automatically detect foo.R as a R file. Is there something else I should add?

Chris

##############
# Enable Languages
menu.language=\
Text|txt|$(keyText)|\
&C / C++|c||\
C&#|cs||\
&Fortran|f90||\
Matlab|m.matlab||\
R|R||\
Shell|sh||\
S&QL|sql||\
TeX|tex||\

imports.include=r tex matlab sql

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

[Chris]

Actually, I found this to be less than a useful solution. Basically I
just wanted to enable R and not disable the other language supports
which my way does. So I ended up changing permissions on the
SciTEGlobal.properties and removing r from imports.exclude and the #
from the R language. Is this a good option? How could I have achieved
this in just the user properties?
Chris

On Apr 26, 8:44 am, Christopher David Desjardins

[Chris]

One last thing I swear. I apologize for spamming.

I just want to recap my issues.

1) What is the best way to enable R support without disabling other
support?

2) How can I make Scite automatically detect the correct language?
Presently I have to tell Scite that I have opened a .tex file, .R
file, etc. to get proper syntax highlighting

3) Also it appears I can run pdflatex, etc. from Scite. How can I
enable this?

4) Will I receive Scite-Mac OSX update for free?

These are my questions and I'll wait till I get a response. But if you
don't want to read the other emails that is my recap.

Chris

[Philippe Lhoste]

On 26/04/2012 16:58, Chris wrote:
> One last thing I swear. I apologize for spamming.

That's OK, at least your try to solve your issues by yourself!

> I just want to recap my issues.

Good idea. :-)

> 1) What is the best way to enable R support without disabling other
> support?

Avoid changing the rights of SciTEGlobal.properties, because this is
likely to be overwritten on the next upgrade of SciTE.
I did that for years, out of habit, but now that support of
SciTEUser.properties is complete, I dropped this bad habit.

Using imports.include is probably the way to go.
Now, I just rewrote in the user file:
imports.exclude=\
<long list of lexers>

import *

You can copy stuff from Global to User, the latter will be taken in account.
This applies particularly to menu.language.
But you can also, if all you want is to add lexers, do:
menu.language=$(menu.language)\
R|R||\
<etc.>

I think it can work...

> 2) How can I make Scite automatically detect the correct language?
> Presently I have to tell Scite that I have opened a .tex file, .R
> file, etc. to get proper syntax highlighting

In r.properties, you have:

file.patterns.r=*.R;*.rsource;*.S;
file.patterns.r.like=$(file.patterns.r)

lexer.$(file.patterns.r)=r

This should be enough to automatically activate the R lexer when opening
a R file.

Note: I am a Windows user, occasionally a Linux user, I don't know if
Macs have any specificity.

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

[Christopher David Desjardins]

On Apr 26, 2012, at 12:02 PM, Philippe Lhoste wrote:

> On 26/04/2012 16:58, Chris wrote:
>> One last thing I swear. I apologize for spamming.
>
> That's OK, at least your try to solve your issues by yourself!
>
>> I just want to recap my issues.
>
> Good idea. :-)
>
>> 1) What is the best way to enable R support without disabling other
>> support?
>
> Avoid changing the rights of SciTEGlobal.properties, because this is likely to be overwritten on the next upgrade of SciTE.
> I did that for years, out of habit, but now that support of SciTEUser.properties is complete, I dropped this bad habit.
>
> Using imports.include is probably the way to go.
> Now, I just rewrote in the user file:
> imports.exclude=\
> <long list of lexers>
>
> import *
>
> You can copy stuff from Global to User, the latter will be taken in account.
> This applies particularly to menu.language.
> But you can also, if all you want is to add lexers, do:
> menu.language=$(menu.language)\
> R|R||\
> <etc.>
>

> I think it can work…

Thanks this helps.

>
>> 2) How can I make Scite automatically detect the correct language?
>> Presently I have to tell Scite that I have opened a .tex file, .R
>> file, etc. to get proper syntax highlighting
>
> In r.properties, you have:
>
> file.patterns.r=*.R;*.rsource;*.S;
> file.patterns.r.like=$(file.patterns.r)
>
> lexer.$(file.patterns.r)=r
>
> This should be enough to automatically activate the R lexer when opening a R file.
>
> Note: I am a Windows user, occasionally a Linux user, I don't know if Macs have any specificity.

Unfortunately that doesn't seem to work. It appears that no lexer ever gets activated. For example, if I open a .tex file that lexer doesn't get activated either. Perhaps this is a Mac thing? Or some sort of bug that requires me to activate the language in the language menu?

Thanks,
Chris

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

[Neil Hodgson]

Chris:

> 1) What is the best way to enable R support without disabling other
> support?

Copy imports.exclude from global options to user options and remove 'r' from the set of files excluded. Properties in user options override those in global properties. As Philippe says, make changes in user options not global options as that file will be replaced with the next release.

> 2) How can I make Scite automatically detect the correct language?
> Presently I have to tell Scite that I have opened a .tex file, .R
> file, etc. to get proper syntax highlighting

The quick way is to save it with a '.rsource' extension.

R is unusual in that it has an upper case extension. Most Unixes are case-sensitive for file names and Windows is case-insensitive so there is code to handle this difference. OS X is in the middle, being a case-insensitive Unix and I think there is a bug caused by this getting in the way. I'll look into it.

> 3) Also it appears I can run pdflatex, etc. from Scite. How can I
> enable this?

If a TeX file is loaded and recognized then the compile command should run pdflatex. If this isn't working, you may gave to copy the property for this from tex.properties to user options and fix it.

> 4) Will I receive Scite-Mac OSX update for free?

Yes. The next release is the first that will be sandboxed which may cause problems. You should back up your current version before allowing the App Store to update SciTE.

One of the App Store rules is that I have to provide a support URL which is linked from the App Store SciTE page. You can use that but its more likely you will find people who know about particular languages here - I have never used R.

Neil

[Neil Hodgson]

Me:

> R is unusual in that it has an upper case extension. Most Unixes are case-sensitive for file names and Windows is case-insensitive so there is code to handle this difference. OS X is in the middle, being a case-insensitive Unix and I think there is a bug caused by this getting in the way. I'll look into it.

This will be fixed in the release after the next since the next release is already in the App Store review pipeline.

Neil

[Christopher David Desjardins]

Thanks Neil for getting back to me. Here's my recap.

1) Using .rsource works for me. I will try to remember to do this until this gets fixed. I think most people use .R and .r somewhat interchangeable. I generally always use .R.

2) TeX works. Apparently, I didn't save my file with the .tex extension. Doh. However, when I run pdflatex on my .tex file, it doesn't find my styles that I have created myself and placed in "/Users/chris/Library/texmf/tex/latex/". Running pdflatex from Terminal on the .tex file does find it. Any ideas why it doesn't?

3) That's great to hear about SciTE and no worries about not fixing the R bug until the next next release. I really appreciate your quick response.

4) Any idea how I can use a spell checker? I am only interested in this really for LaTeX and I could use TeXShop to spell at the end and SciTE to actually write the document. Though it would be nice. Is it possible to use Apple's spell check?

I am glad to have found SciTE it's pretty slick and super fast.

Thanks,
Chris

[Neil Hodgson]

Christopher David Desjardins:

> 2) TeX works. Apparently, I didn't save my file with the .tex extension. Doh. However, when I run pdflatex on my .tex file, it doesn't find my styles that I have created myself and placed in "/Users/chris/Library/texmf/tex/latex/". Running pdflatex from Terminal on the .tex file does find it. Any ideas why it doesn't?

Interactive sessions are different to running a shell with pipes and this will get worse with the next release due to the sandbox. One difference is in environment variables including the path. Run "set" in a terminal and in the SciTE output pane to seek out any differences. Add variables missing from SciTE to ~/.bashprofile for this version and ~/.bashrc for the next.

> 4) Any idea how I can use a spell checker? I am only interested in this really for LaTeX and I could use TeXShop to spell at the end and SciTE to actually write the document. Though it would be nice. Is it possible to use Apple's spell check?

There is no spell checker built-in. There has been some work by others. Search for "spell" in the mailing list archive.

Neil

[Christopher David Desjardins]

Below is my output from set. Unfortunately I have no idea what to make of it. I tried just copying everything from Terminal's set output to .bashprofile but that didn't work. Thanks and I'll look into the spell check stuff.

Here is set from SciTE
>set
BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
BASH_EXECUTION_STRING=set
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="3" [1]="2" [2]="48" [3]="1" [4]="release" [5]="x86_64-apple-darwin11")
BASH_VERSION='3.2.48(1)-release'
DIRSTACK=()
EUID=501
GROUPS=()
HOSTNAME=Christopher-David-Desjardinss-MacBook-Pro.local
HOSTTYPE=x86_64
IFS=$' \t\n'
MACHTYPE=x86_64-apple-darwin11
OPTERR=1
OPTIND=1
OSTYPE=darwin11
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/texbin:/Applications/Mplus
PIPESTATUS=([0]="0")
PPID=21724
PS4='+ '
PWD=/Users/chris/Dropbox/Documents/university/dissertation/oral_exam_presentation
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments
SHLVL=1
TERM=dumb
TMPDIR='/private/var/folders/qc/hcwz29kj0f70tbd3p_k5sdkw0000gn/T/Cleanup At Startup'
UID=501
_=TMPDIR


Here is set from Terminal
chris$ set
Apple_PubSub_Socket_Render=/tmp/launch-ZAz3gE/Render
Apple_Ubiquity_Message=/tmp/launch-rkHSFg/Apple_Ubiquity_Message
BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="3" [1]="2" [2]="48" [3]="1" [4]="release" [5]="x86_64-apple-darwin11")
BASH_VERSION='3.2.48(1)-release'
COLUMNS=105
COMMAND_MODE=unix2003
DIRSTACK=()
DISPLAY=/tmp/launch-yyGYS3/org.x:0
EUID=501
GROUPS=()
HISTFILE=/Users/chris/.bash_history
HISTFILESIZE=500
HISTSIZE=500
HOME=/Users/chris
HOSTNAME=Christopher-David-Desjardinss-MacBook-Pro.local
HOSTTYPE=x86_64
IFS=$' \t\n'
LANG=en_US.UTF-8
LINES=51
LOGNAME=chris
MACHTYPE=x86_64-apple-darwin11
MAILCHECK=60
OLDPWD=/Users/chris
OPTERR=1
OPTIND=1
OSTYPE=darwin11
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/texbin:/Applications/Mplus
PIPESTATUS=([0]="0")
PPID=22009
PROMPT_COMMAND='update_terminal_cwd; '
PS1='\h:\W \u\$ '
PS2='> '
PS4='+ '
PWD=/Users/chris
SHELL=/bin/bash
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
SHLVL=1
SSH_AUTH_SOCK=/tmp/launch-Wek511/Listeners
TERM=xterm-256color
TERM_PROGRAM=Apple_Terminal
TERM_PROGRAM_VERSION=303
TERM_SESSION_ID=97897B1B-42A3-404C-BBCC-395BEBAD4A23
TMPDIR='/private/var/folders/qc/hcwz29kj0f70tbd3p_k5sdkw0000gn/T/Cleanup At Startup'
UID=501
USER=chris
_=.bashprofile
__CF_USER_TEXT_ENCODING=0x1F5:0:0
update_terminal_cwd ()
{
local SEARCH=' ';
local REPLACE='%20';
local PWD_URL="file://$HOSTNAME${PWD//$SEARCH/$REPLACE}";
printf '\e]7;%s\a' "$PWD_URL"

[Neil Hodgson]

Christopher David Desjardins:

> Below is my output from set. Unfortunately I have no idea what to make of it. I tried just copying everything from Terminal's set output to .bashprofile but that didn't work.

Did you remember to prefix every setting with export so it is visible outside the script? You can also try individual settings from the SciTE output pane using 'env' such as:
env COLUMNS=40 pdflatex $(FileNameExt)

Neil

[Christopher David Desjardins]

Hi Neil,
I tried this in my .bashprofile. Is this what you had in mind? Because it still doesn't work. Perhaps I am better off just copying this to my main texmf directories?

Christopher-David-Desjardinss-MacBook-Pro:~ chris$ cat .bashprofile
export Apple_PubSub_Socket_Render=/tmp/launch-ZAz3gE/Render
export Apple_Ubiquity_Message=/tmp/launch-rkHSFg/Apple_Ubiquity_Message
export BASH=/bin/bash
export BASH_ARGC=()
export BASH_ARGV=()
export BASH_LINENO=()
export BASH_SOURCE=()
export BASH_VERSINFO=([0]="3" [1]="2" [2]="48" [3]="1" [4]="release" [5]="x86_64-apple-darwin11")
export BASH_VERSION='3.2.48(1)-release'
export COLUMNS=105
export COMMAND_MODE=unix2003
export DIRSTACK=()
export DISPLAY=/tmp/launch-yyGYS3/org.x:0
export EUID=501
export GROUPS=()
export HISTFILE=/Users/chris/.bash_history
export HISTFILESIZE=500
export HISTSIZE=500
export HOME=/Users/chris
export HOSTNAME=Christopher-David-Desjardinss-MacBook-Pro.local
export HOSTTYPE=x86_64
export IFS=$' \t\n'
export LANG=en_US.UTF-8
export LINES=51
export LOGNAME=chris
export MACHTYPE=x86_64-apple-darwin11
export MAILCHECK=60
export OLDPWD=/Users/chris
export OPTERR=1
export OPTIND=1
export OSTYPE=darwin11
export PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/texbin:/Applications/Mplus
export PIPESTATUS=([0]="0")
export PPID=22009
export PROMPT_COMMAND='update_terminal_cwd; '
export PS1='\h:\W \u\$ '
export PS2='> '
export PS4='+ '
export PWD=/Users/chris
export SHELL=/bin/bash
export SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
export SHLVL=1
export SSH_AUTH_SOCK=/tmp/launch-Wek511/Listeners
export TERM=xterm-256color
export TERM_PROGRAM=Apple_Terminal
export TERM_PROGRAM_VERSION=303
export TERM_SESSION_ID=97897B1B-42A3-404C-BBCC-395BEBAD4A23
export TMPDIR='/private/var/folders/qc/hcwz29kj0f70tbd3p_k5sdkw0000gn/T/Cleanup At Startup'
export UID=501
export USER=chris
_=.bashprofile
__CF_USER_TEXT_ENCODING=0x1F5:0:0
export update_terminal_cwd ()

{
local SEARCH=' ';
local REPLACE='%20';
local PWD_URL="file://$HOSTNAME${PWD//$SEARCH/$REPLACE}";
printf '\e]7;%s\a' "$PWD_URL"
}

[Christopher David Desjardins]

FYI,
I did copy my files to the main texmf directory and pdflatex now works as expected. However, if it's possible to have SciTE also see and use my personal texmf directory located at "/Users/chris/Library/texmf/" that would be the best solution.
Cheers,
Chris

[Neil Hodgson]

Christopher David Desjardins:

> I did copy my files to the main texmf directory and pdflatex now works as expected. However, if it's possible to have SciTE also see and use my personal texmf directory located at "/Users/chris/Library/texmf/" that would be the best solution.

If that is a good solution for you then you can change the command to perform a copy and then run pdflatex. Will this be a good change for everyone? Does this directory always have the same name for other people?

Neil

[Christopher David Desjardins]

I think most people will have tex files in the main directory and then any personal tex files will typically be stored in:

/Users/username/Library/texmf

I think if pdflatex was set up to look in both the root directory and the user directory by default this would be a good change for most people.
Chris

[Homme, James]

Hi,
I am collecting browser bookmarks for documentation for SciTe, because I'm a new user. I think that I might want to write a script or two and hook it or them up to a key that would make them run against the current selection or current line, for example, give me a menu of HTML tags and then enclose the current selection or current line with the opening and closing tag. Would someone please tell me where to read about how to do this?

Thanks.

Jim

________________________________

This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates.

[Neil Hodgson]

Christopher David Desjardins:

> I think if pdflatex was set up to look in both the root directory and the user directory by default this would be a good change for most people.

How do you tell pdflatex where to look?

Neil

[Christopher David Desjardins]

I just run pdflatex from the Terminal and it just knows to look in these paths by default. I think the MacTeX default settings do this already.
Chris

Chris

[Philippe Lhoste]

On 30/04/2012 13:27, Homme, James wrote:
> I am collecting browser bookmarks for documentation for SciTe,
> because I'm a new user. I think that I might want to write a script
> or two and hook it or them up to a key that would make them run
> against the current selection or current line, for example, give me a
> menu of HTML tags and then enclose the current selection or current
> line with the opening and closing tag. Would someone please tell me
> where to read about how to do this?

I am not sure how it is related to the "R and Scite-Mac OSX" thread, but
whatever.

Information about scripting SciTE can be found at the
http://www.scintilla.org/SciTELua.html page.
You can find examples of scripts on the Net. For what it is worth, my
personal file is at
http://bazaar.launchpad.net/~philho/+junk/SciTESettings/view/head:/SciTEStartup.lua

[Christopher David Desjardins]

I upgraded to 3.1 and SciTE can no longer find pdflatex. I believe this is expected and based on http://www.scintilla.org/Sandbox.html

I added "/usr/local/texlive/2011/bin/x86_86-darwin" to the Allow Access dialog box. However, pdflatex with:

>pdflatex oral_exam_cddesjardins.tex

shell-init: error retrieving current directory: getcwd: cannot access parent directories: Operation not permitted

/bin/bash: pdflatex: command not found

>Exit code: 0

Any ideas?

[Christopher David Desjardins]

Hi,

I am wondering if there is a way to turn off the hidden files from the open dialog box on SciTE 3.1 on a Mac? I found this

http://groups.google.com/group/scite-interest/browse_thread/thread/9c4ca51aac35d1a6

But setting  fileselector.show.hidden=0 doesn't do anything.

Thanks,

Chris

[Neil Hodgson]

Christopher David Desjardins:

> >pdflatex oral_exam_cddesjardins.tex
> shell-init: error retrieving current directory: getcwd: cannot access parent directories: Operation not permitted

You have probably opened the file oral_exam_cddesjardins.tex in SciTE. This has provided SciTE with permission to read and write just the file oral_exam_cddesjardins.tex. It does not have any permissions for the directory that file is in. A consequence of this is that SciTE (and programs it runs) can set the current directory to that directory but then cannot ask what the name of that directory is (getcwd). This can be fixed by allowing access to that that directory with the Allow Access dialog.

>
> /bin/bash: pdflatex: command not found
> >Exit code: 0

You should check the path in the output pane and ensure it is the same as in Terminal. If not set the path in ~/.bashrc. Ensure ~/.bashrc is in Allow Access.

Neil

[Neil Hodgson]

Christopher David Desjardins:

http://groups.google.com/group/scite-interest/browse_thread/thread/9c4ca51aac35d1a6

But setting  fileselector.show.hidden=0 doesn't do anything.

   fileselector.show.hidden has been removed from the GTK+ version. I'll look into adding fileselector.show.hidden to the OS X version. Adding an extra control to the open dialog to control whether hidden files are visible isn't safe at the moment since sandboxing has made the open dialog more flakey than before.

   Neil

[Christopher David Desjardins]

Hi,
I am sorry to continue this thread as I can't solve my problem yet. Hopefully this isn't too big of a deal. I added ~/.bashrc to the Allow Access Dialog as well as the top directory that would host any and all .tex files I would work. Now I am getting this message.

>pdflatex oral_exam_cddesjardins.tex
lstat(./pdflatex) failed ...
./pdflatex: No such file or directory
warning: kpathsea: configuration file texmf.cnf not found in these directories: $SELFAUTOLOC:$SELFAUTODIR:$SELFAUTOPARENT:$SELFAUTOLOC/share/texmf-local/web2c:$SELFAUTODIR/share/texmf-local/web2c:$SELFAUTOPARENT/share/texmf-local/web2c:$SELFAUTOLOC/texmf-local/web2c:$SELFAUTODIR/texmf-local/web2c:$SELFAUTOPARENT/texmf-local/web2c:$SELFAUTOLOC/share/texmf/web2c:$SELFAUTODIR/share/texmf/web2c:$SELFAUTOPARENT/share/texmf/web2c:$SELFAUTOLOC/texmf/web2c:$SELFAUTODIR/texmf/web2c:$SELFAUTOPARENT/texmf/web2c.
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)

kpathsea: Running mktexfmt pdflatex.fmt
mktexfmt: No such file or directory
I can't find the format file `pdflatex.fmt'!

All I add to ~/.bashrc was
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/texbin:/Applications/Mplus:

Any continued help and I would be very grateful.

Also, any chance of adding a BibTeX entry in the Tools Menu by default for .tex files? Seems like it would be useful. I have done this for myself using the Help manual.

Chris

[Neil Hodgson]

Christopher David Desjardins:

> warning: kpathsea: configuration file texmf.cnf not found in these directories:

...

> kpathsea: Running mktexfmt pdflatex.fmt
> mktexfmt: No such file or directory
> I can't find the format file `pdflatex.fmt'!

OK, I think it wants the 3 files mentioned (texmf.cnf, mktexfmt, and pdflatex.fmt) added to Allow Access. Find them, either using the command line 'find' command from a Terminal or the search box in a Finder window and then add their directories. There's probably a parent directory containing all the TeX stuff and allowing access to it will make all of these visible.

> Also, any chance of adding a BibTeX entry in the Tools Menu by default for .tex files? Seems like it would be useful. I have done this for myself using the Help manual.

All the existing commands and settings come from TeX users since these aren't areas that I am familiar with. If someone contributes reasonable settings for BibTeX, they can be distributed.

Neil

[Christopher David Desjardins]

OK, I finally solved the problem. In case anyone else has the issue here is what I did.

First, I added everything from echo $PATH to ~/.bashrc

PATH=stuff:from:echo$PATH
export PATH

Second, I added the following to "Allow Access"
~/.bashrc
/Where/I/Store/My/TeX/Files
/usr/local/texlive

And now I have it working.

RE: BibTeX here's what I got in SciTEUser.properties

command.name.2.$(file.patterns.tex)=BibTeX
command.name.2.$(file.patterns.latex)=BibTeX
command.name.2.$(file.patterns.context)=BibTeX
command.2.$(file.patterns.tex)=bibtex $(FileName)
command.2.$(file.patterns.latex)=bibtex $(FileName)
command.2.$(file.patterns.context)=bibtex $(FileName)

Finally, if someone is using Sweave with SciTE here's how I got the Sweave.sh script to work

1) Allow Access to /tmp

2) Add the following to SciTEUser.properties
file.patterns.r=*.R;*.rsource;*.S;*.r;*.Rnw;
command.name.3.$(file.patterns.r)=Sweave
command.3.$(file.patterns.r)=Sweave.sh -old="open -a Skim.app" $(FileNameExt)

3) Add the location of Sweave.sh to ~/.bashrc

You should be good to go after this.

If I take the time to create a lexer for .Rnw files could this potentially get added? These are .tex files that include R code. I am not sure the best way to do this and if anyone already has a lexer that would be greatly appreciated.

Still haven't figured out spellchecking but I'll keep looking ;)

Cheers,
Chris

[Neil Hodgson]

Christopher David Desjardins:

OK, I finally solved the problem. In case anyone else has the issue here is what I did.

First, I added everything from echo $PATH to ~/.bashrc

PATH=stuff:from:echo$PATH
export PATH

Second, I added the following to "Allow Access"
~/.bashrc
/Where/I/Store/My/TeX/Files
/usr/local/texlive

   One of the reasons for Sandbox.html was so that application-specific instructions could be published. Updated http://www.scintilla.org/Sandbox.html with a TeX section.

   The only other support question I have received for the OS X 3.1.0 release was about pdflatex too.

If I take the time to create a lexer for .Rnw files could this potentially get added?

   Yes, a well-written lexer could be added.

   Neil

[Christopher David Desjardins]

One other thing that I've noticed, though it's trivial to me at least, is that Spotlight doesn't seem to show SciTE if I search for it there. It did with 3.0.4. Maybe it's an issue with just my laptop?
Chris

[Neil Hodgson]

Christopher David Desjardins:

> One other thing that I've noticed, though it's trivial to me at least, is that Spotlight doesn't seem to show SciTE if I search for it there. It did with 3.0.4. Maybe it's an issue with just my laptop?

Spotlight doesn't search some of the places it used to. Files in ~/Library don't seem to show up.

Neil

[Christopher David Desjardins]

So this isn't a bug? It seems like SciTE should show up when searched for in Spotlight. If I search for Safari, Chrome, Mail, etc., that are in Applications folder they show up. SciTE is also in the Applications folder. It just seems strange.
Chris

[Neil Hodgson]

Christopher David Desjardins:

> So this isn't a bug? It seems like SciTE should show up when searched for in Spotlight.

I'd expect it to show up too. There haven't been any changes in SciTE aimed at Spotlight. Its possible the sandbox changes affect whether SciTE gets indexed.

Neil

[Neil Hodgson]

fileselector.show.hidden will be in the next OS X release with the default being to show hidden files.

Neil