I am trying to install the Dummy package to my laptop.
I have installed WAMP and i have placed the dummy package into the WWW directory.
However when i go to my Localhost from WAMP and click on the dummy page, instead of showing me the installation screen it shows my the directory index.
to create ENABLE_INSTALL_TOOL just use command line
win+r -> type cmd -> navigate to directory -> type: echo > ENABLE_INSTALL_TOOL
Dummy package has no sources inside, you can see, there's no even index.php file.
Use Source + Dummy which will give you an empty TYPO3 system or even better Introduction Package for learning purposes - working and containing lot of samples.
To create ENABLE_INSTALL_TOOL make sure that your system displays files' names with extension ie: open with the Windows Explorer folder where you unziped the package and make sure that it can see filenames as INSTALL.txt (not only INSTALL) if it doesn't you need to search in options of Windows Explorer...)
Then go to folder typo3conf and create just common, empty file ENABLE_INSTALL_TOOL.txt and finally chane it's name and remove .txt extension.
TYPOe install tool will be satisfied.
Related
I cannot use the simple installation code because a proxy blocks my way out. Unfortunately, I just don't get the instructions on the webpage.
1. Click the Preferences > Browse Packages… menu
2. Browse up a folder and then into the Installed Packages/ folder
3. Download Package Control.sublime-package and copy it into the Installed Packages/ directory
4. Restart Sublime Text
What exactly does 2. mean? I guess I literally don't understand what "Browse up a folder and then into..." means.
I did click on the Browse Packages menu and used the popup explorer window to create a folder in my documents directory called Installed Packages. But what's next? Since I am just in a regular Explorer window, it I don't see how sublime now knows about this folder.
In Sublime Text, click the Preferences > Browse Packages… menu
this opens Windows Explorer in the path %AppData%\Roaming\Sublime Text 3\Packages.
Browse up a folder
go up one folder level, the equivalent of cd .. in the command prompt. So basically, you want to be in %AppData%\Roaming\Sublime Text 3.
You can do this using the breadcrumbs in the address bar - using the above image as a guide, click on Sublime Text 3. Alternatively, press Backspace to go up a folder level. (Normally it will go back one history level, but in this case there is no history because it is a new Explorer window, so it will go up a directory in the folder hierarchy.)
and then into the Installed Packages folder
Double click on the Installed Packages folder to navigate into it.
Download Package Control.sublime-package and copy it into the Installed Packages directory
So you will have a file called Package Control.sublime-package in the %AppData%\Roaming\Sublime Text 3\Installed Packages folder.
Restart Sublime Text
Close ST and launch it again.
For Mac users, for No. 2, you'll most likely see this. That is the Packages file
To be able to browse up a folder and view the Installed Packages:
Then from there, download using the link and put it in the installed package folder, there you go!
I'm attempting to install the 'Iris Dark' theme on my Ubuntu 14.04 machine.
I'm using gnome-3, and the gnome tweak tool.
I've downloaded, extracted and then moved the theme into my theme folder like so.
unzip /home/admin/Desktop/IrisDark.zip /home/admin/Desktop/IrisDark
sudo cp -r /home/admin/Desktop/IrisDark /usr/share/themes
When I check the gnome tweak tool, it doesn't show up as a theme for either 'Windows' or GTK+. I am able to install other themes using the same method, only having trouble with this specific one.
When I try to open the folder I've just copied in my themes folder, I get 'This location could not be displayed, you do not have the nessecary permissions.."
This does not happen with any other themes I move into that folder, I only lack the read permission for this particular theme. I assume that the tweak tool is also running into that permissions error, and that's why it can't find it, I don't have any idea how I could fix this though.
EDIT: Moving the zipped file to the themes folder, and then unzipping it produces the same result.
The problem was eventually fixed by creating my own themes folder, which I had permissions over.
cd ~
mkdir .themes
cp -r /home/admin/Desktop/IrisDark ~/.themes
Turns out your not supposed to use the systems themes folder, but create your own.
I also experienced the same challenge. I will like to state the procedures that I took to make mine to work, and then you can check to see if you got it wrong somewhere.
Here are the steps
First install the Gnome Tweak Tool from the terminal
sudo apt-get install gnome-tweak-tool
Next, go to GNOME website GNOME Website and download the theme of your choice. They are usually in zipped files, and may be in various variants.
Extract the downloaded files to the ~/.themes/ (home/.themes) directory - to install for current user only. You can press Ctrl + H to show hidden folders. Create the themes folder if you don't have it yet.
Or sudo extract them to the /usr/share/themes/ (home/usr/share/themes) folder - to apply them globally.
sudo tar -xf Folder-Name.tar.xz -C /usr/share/themes
Restart GNOME Tweaks tool. You should see the manually installed GNOME themes in the Tweak tool now. You can configure or enable the newly installed themes here.
This technique for GTK Themes also applies for Icon Themes
That's all
I hope this helps
How can I install a sublimetext3 package manually, without the package control. I am trying to fix a bug in an existing package, therefore I need a way to test my changes.
what are the naming conventions to be followed when naming the zip file?
Where do I place it?
what other configurations I have to do?
Download the ZIP, and then place it in your Packages directory which can be found by doing Sublime Text -> Preferences -> Browse Packages...
what are the naming conventions to be followed when naming the zip file? Where do I place it? what other configurations I have to do?
This really depends on the specific package you are downloading. For some packages, you can name it whatever you want. For others, the name has to be exact. If you are downloading these packages manually from GitHub, I urge you to read the documentation in the README. They usually provide instructions for manual installation. For example, if you wanted to download the Spacegray theme manually, it tells you to download the ZIP, unzip the folder, and rename it to Theme - Spacegray.
Depending on your OS, your package directory might be one of these and for most of the packages, just extract the content to this folder (with it's root folder as the name)
Linux: ~/.config/sublime-text-3/Packages
OS X: ~/Library/Application Support/Subime Text 3/Packages
Windows: %APPDATA%\\Sublime Text 3
I am trying to fix a bug in an existing package, therefore I need a
way to test my changes.
I was in the same situation. The accepted answer didn't work for me because Package Control would automatically remove the folder. I found this to be helpful:
https://packagecontrol.io/docs/customizing_packages
Sublime Text 3 offers the most options for overriding a package. By
default, packages will be installed by placing a .sublime-package file
in the Install Packages/ folder. Then users may override individual
files in the package by creating a folder Packages/{Package Name}/ and
placing edited files in there.
Another approach is PackageResourceViewer, which allows you to extract and override individual files from packages, including the built-in packages.
The best answer I think, so far, is this one by #Andreas Haferburg.
The most-upvoted answer also has some really useful information, such as the link to the spacegray package which states:
Manual
You can also install the theme manually:
Download the .zip
Unzip and rename the folder to Theme - Spacegray
Copy the folder into Packages directory, which you can find using the menu item Sublime Text -> Preferences -> Browse Packages...
That is where I first learned about the existence of the Packages folder and how to find its path.
Using those answers together, plus putting in about 1 weekend worth of work into learning about how Sublime Text packages and syntax highlighting work, I wrote the following "Developer Notes & Package Development Tutorial", on GitHub, as well as these "manual installation" instructions.
In short, to "install a package" withOUT Package Control, all you need to do is put the package into your Sublime Text Packages folder, whose path can be found by going to Preferences --> Browse Packages.... The folder name can be anything. It only needs to match what is inside the Installed Packages dir (which is at the same level as the Packages dir) if you want to override an already-installed package which was previously installed by Package Control in "packed" (zip file) format.
The main link you should study, aside from my tutorial, is this: https://packagecontrol.io/docs/customizing_packages.
1. How to manually install a package
Here are some of the key quotes and instructions from my manual installation instructions and tutorial.
Again, note that I am only requiring that the name in the Packages folder be something specific like gcode in the instructions below because my instructions are intended to override a Package-Control-installed package the reader may already have installed. If you want to install for the first time, or make a new package, the folder name you use inside the Packages folder can be anything.
2. Manual installation
In Sublime Text, find the path to your Packages folder by clicking Preferences --> Browse Packages.... This will open up your GUI file manager to the path where Sublime Text packages are stored. For me on Linux Ubuntu 20.04, that's /home/gabriel/.config/sublime-text-3/Packages (even though I am running Sublime Text 4).
Now, extract this package to that folder.
Option 1: the GUI way: click the green "Code" button above --> "Download ZIP" --> save the zip file, extract it to your Packages path above, and rename it to gcode.
OR Option 2 [what I prefer]: the command-line way:
# --------------
# Option 2.A: clone the repo directly into your "Packages" dir
# --------------
# cd to the Packages dir (change this path according to your Packages path above)
cd "$HOME/.config/sublime-text-3/Packages"
# clone the repo
git clone https://github.com/ElectricRCAircraftGuy/sublime_gcode.git
# rename the repo dir to "gcode"
mv sublime_gcode gcode
# --------------
# OR Option 2.B [what I prefer]: clone the repo into wherever you want, and then
# symlink it into your "Packages" dir
# --------------
# clone repo into ~/dev
mkdir -p ~/dev
cd ~/dev
git clone https://github.com/ElectricRCAircraftGuy/sublime_gcode.git
# now symlink it into your Packages dir
ln -si ~/dev/sublime_gcode ~/.config/sublime-text-3/Packages/gcode
That's it! The gcode entry is now instantly available in your syntax highlighting menu.
Developer Notes & Package Development Tutorial
...
...
...
Sublime Text packages and syntax highlighting--how it all works
And here are some really important notes about Sublime Text packages and how Package Control works:
1. Sublime Text packages
Any folder inside of your Sublime Text Packages folder (found via Preferences --> Browse Packages...) is automatically instantly loaded by Sublime Text as a "package".
Packages installed by the Package Control package, however, come in two types:
Packed: most packages installed by Package Control are "packed" into a zip file named packageName.sublime-package and are located inside the Installed Packages dir which is at the same level as the Packages dir.
If you manually create a dir inside the Packages dir and name it packageName (to match the packed file above), then any files in it with the same name as those in the packed package will override those in the packed package. See the "Overrides" section here: https://packagecontrol.io/docs/customizing_packages.
Unpacked: any package which is installed in the Packages dir is unpacked.
Developers can tell Package Control to unpack a package installed by Package Control by placing a file named .no-sublime-package at the root of their repo. See here: https://packagecontrol.io/docs/submitting_a_package.
Unpacked packages are required if they contain binary executables which need to be run by the system, for instance, as they apparently can't run from inside the packed zip file.
2. Syntax highlighting
Hopefully I got all of this straight.
If you want to learn more about Syntax Highlighting in Sublime Text, and how it maps to scope entries in your Color Scheme, read my tutorial.
2. Test your changes
I am trying to fix a bug in an existing package, therefore I need a way to test my changes.
See also this section in my tutorial:
To modify and test changes to this package locally...
...in case you'd like to change it or contribute to it, follow the "manual installation" instructions above. If you have already installed it via Package Control, then what is in your /home/$USERNAME/.config/sublime-text-3/Packages/gcode folder will override what is in your /home/$USERNAME/.config/sublime-text-3/Installed Packages/gcode.sublime-package zip file which Package Control installed, so long as the folder and file names are the same.
Modify any files in the Packages/gcode dir as desired. Each time you save, the changes will instantly be reflected in all Sublime Text editors you have open. As a quick test:
Open a gcode file.
Click your cursor on some text in the file.
Use the Tools --> Developer --> Show Scope Name trick to see what the scope is for that text.
Open the corresponding *.sublime-syntax file.
Change or delete the regular expression in the match entry for that corresponding scope you just found, so that it no longer matches the text on which you placed your cursor.
Save the *.sublime-syntax file and you will instantly see the formatting of that text in the gcode file change.
Undo your change to the match entry and save again. The formatting will return to how it was.
Go to Preferences --> Customize Color Scheme, and add a custom rules entry for that scope, with new formatting for that scope. Save it and watch the formatting instantly change again. Delete that custom entry when done, if desired.
Is this even possible? I am trying to script this install of IBM Clearcase and the path to it is like:
../disk1/InstallerImage_linux_gtk.x86/install.xml
The script barfs at the .x86 and it says "No such file or directory."
So I tried to just do vim ../disk1/InstallerImage_linux_gtk.x86/install.xml in a terminal and it opens the .x86 like a folder and allows you to select a file to edit instead of opening it directly.
Is there a way around this? Would the only way be to rename the folder before, do the sed voodoo and then move it back with the . in the name?
I guess I missed the obvious. I guess I could cd to the directory first and then do sed -i '' install.xml.
More info:
RHEL 6.5
Bash Script
You need to script a silent ClearCase installation, using one of the sample response files for Rational ClearCase.
That would avoid the need to open any file in vim.
See "Installing silently", which involves the following steps:
Run a silent install of Installation Manager using the Installation Manager installer.
Obtain a copy of the product response file and update it for your environment. If you want to record a response file using Installation Manager, see the Installation Manager information center for instructions.
Run a silent install of the Rational product using the Installation Manager.
I think you have created a file with a seriously strange file name. Do this:
$ cd /path/to/where/you/run/the/script/from
$ file ..
$ file ../disk1
$ file ../disk1/InstallerImage_linux_gtk.x86
$ file ../disk1/InstallerImage_linux_gtk.x86/install.xml
Every component of the relative path (beginning with "..") must be a directory. Only the final line should claim to be an ordinary file.
I'm trying to install the extension for Visual Studio 2012 that allows emacs key-bindings.
I'm following through the steps here:
Emacs Keybindings in Visual Studio 2012 or 2013
I'm up to step 5:
Run the vsik file as administrator. This is required so the extension
can write Emacs.vsk into the program files folder. I wasn't sure the
best way to do this so I ran a command prompt as admin and then
executed start emacsemulations.vsik from the prompt.
So, running emacsemulations.vsix from an administrator command prompt,
I get the following error "This VSIX package is invalid because it does not contain the file extension.vsixmanifest at the root."
I'm not changing any of the file names inside the package.
I'm thinking this may have something to do with how windows zips up the file -- I'm able to recreate the problem simply by unzipping and rezipping the EmacsEmulation.vsix file without changing the contents of the vsix package.
If anyone has any suggestions on how to fix, or even better, the actual updated vsix file itself, I'd be very grateful!
The issue you have relies on the way you are zipping your file, what you should do is zip all files inside the folder you created (in this case, "EmacsEmulations") when you unzipped it.
Step into the EmacsEmulations folder.
Select all files.
Add to .zip
Rename the .zip output to EmacsEmulations.vsix
I'm trying to get this extension to work too, so good luck!