Hi,
i would like to display popup / hints / overlays at certain position in code, so I can show the error where the occur.
Is that somehow possible with the current plugin API? Maybe with dialog2 and custom nibs?
Thank you
Fabian
Hello Everyone,
This has probably been discussed before when Apple's "El Capitan" came
out. I have only recently upgraded to this OS. I am using Textmate for
writing Latex documents. With the upgrade I loste the functionality of
having .sty-files stored in a dedicated folders (texmf in pre-capitan
times). Where do I put these files now? and more importantly: How to I
tell Textmate (or the Latex Bundle) where to find them?
Best,
Christian
I generally hate Microsoft Word, but I like the way it handles comments i.e. comments are in boxes in the right margin, separated from text. Is it possible to have TextMate handle comments in the same way i.e. hidden or somehow separated from text?
Ross Ahmed
Ecologist
--
07875533906
Twitter: @RossAhmed
LinkedIn: Ross Ahmed
When I go to Bundles > R Console (Rdaemon) > General Control > Start Rdaemon, the blue line goes right to the end put Rdaemon doesn't start up. Why is Rdaemon not starting up?
Ross Ahmed
Ecologist
--
07875533906
Twitter: @RossAhmed
LinkedIn: Ross Ahmed
Hi,
Today I wanted to try a new theme and noticed that the theme menu only
lists the theme's name, so I had to try them all, which is expected.
My issue is that I already knew I wanted a light theme, because I like
them better. I just asked around and at least with the small sample
of people around me, they already know if they prefer light themes or
dark themes.
It looks like themes are already identified as light or dark via their
Semantic Class, so my suggestion is to include this distinction in the
UI somehow. I know this is not something the user will do frequently,
but I think this improvement will cut the time to select a new theme
roughly by half.
--
:: dip
--
Hi all,
I've some strange issues with a shell script for a bundle command. Caused by
a "*" (Asterisk) at the end of the line.
Description:
In a folder I've the following files:
test.md
AAA-some-text.md
The content of test.md is:
In my bundle script I do a lot with the file. One of the things is that I
want to grep the first Header. In this case "# A header with star AAA*".
The shell code is (only the code causing the issue):
#!/bin/bash
[[ -f "${TM_SUPPORT_PATH}/lib/bash_init.sh" ]] && .
"${TM_SUPPORT_PATH}/lib/bash_init.sh"
cd ~/Desktop
contenttitle=`grep -m 1 '^#\{1\}' test.md`
echo $contenttitle
When running "grep -m 1 '^#\{1\}' test.md" in Terminal I get as expected the
first header "# A header with star AAA*", but running the script in TextMate
I get "# A header with star AAA-some-text.md". Really strange..... there is
a replacement of "AAA*" by the filename "AAA-some-text.md" (from the current
folder). And even when more files with "AAA" exist, they also come in the
result of the script. It seems like there is a listing of the directory
performed like "ls AAA*".
Is this a TextMate issue? Or do I something wrong?
Regards,
Feek
NB1: when escaping the * in the markdown file (like \*), the script is
performed right.
NB2: when the AAA* text is in the middle of the line (some text on the
right), the error persists.
--
View this message in context: http://textmate.1073791.n5.nabble.com/Strange-issues-with-a-shell-script-fo…
Sent from the textmate users mailing list archive at Nabble.com.
I’ve never gotten the watch command to work in the LaTeX bundle, and I’d like to see if I can’t troubleshoot it. I’m running OS 10.11.3 and TextMate 2 beta .9. I typeset through the ps->dvips route. When I run the Watch Document command I get this error:
The command `osascript -e tell application "XQuartz" to launch' failed (error code 1).
Can someone point me to the next step?
Thanks,
Kyle
