setxkbmap it
doesn't work.
How i configure the keyboard layout in RDK Video IP (A Yocto Project based Distro)?
The answer is simply:
loadkeys it
Equivalent at:
loadkeys /usr/share/keymaps/i386/qwerty/it.map.gz
Related
reccently, I want to test how does the autoscheduler "Li2018" work on GPU. Firstly, I need to load the plugin of this autoscheduler into my project with function "load_plugin("gradient_autoscheduler")" like the example: https://github.com/halide/Halide/blob/master/apps/gradient_autoscheduler/test.cpp but the biggest problem is, that I cannot generate the plugin on Windows. I have tried to add the "generate_autoscheduler" into the CMakeList.txt in the /apps folder, but it can not work. To compare with autoscheduler "Admas2019" which in the folder /apps/autoscheduler, "Li2018" need a CMakeList.txt to generate the dll plugin, Does some one know how to generate the plugin of "Li2018" on windows? Thanks in advance!
As you have noticed, we don't have a CMake configuration for Li's autoscheduler, so Windows is not supported yet. I'll put this in my TODO list, but contributions are always welcome. It shouldn't be hard to come up with a CMakeLists.txt based on the Makefile content.
I'm trying out yocto (2.0, jethro) and I want to build an image starting from core-image-minimal. This works fine.
Every website out there mention modifying the file build/config/local.conf with (some of) my customization. For example, the target machine (through MACHINE) or some global settings (through EXTRA_IMAGE_FEATURES).
I also need to modify some specific packages and the way to do it is to create a custom layer. So far so good.
What I don't understand is how to "save" all my configuration to version control. I want everything I change to be locate in files that I can commit so that anybody else can reproduce the exact same build (or even contribute to that project). Putting almost everything in build/config/local.conf goes against that goal; the file is under a "build" directory and so I can't just clone a git repo and start the building...
Is it really the way the yocto project works? Or am I missing a different configuration file where I need to put these settings? I though I could place all these in a custom layer but it does not seem to work...
Any idea or suggestion?
Thanks!
Thanks Ross, that clarified it!
Here's some notes about my file organization which I couldn't format into a comment to your answer.
Thanks. So all my custom configurations went into meta-mylayer/conf/distro/mylayer.conf
Almost all my customization went into a layer meta-mylayer, except:
DISTRO which is set in build/conf/local.conf. This is how you tell yocto what you want to build.
MACHINE which is also set in build/conf/local.conf. The reason is that the same image/distro combination could be built for different machines and thus this can't be hard-coded for every images.
Layers are manually added to build/conf/layers.conf. That's the last bit I wish I could moved to my DISTRO or something. For now the folders are git submodules and they are added using bitbake-layers add-layer.
In general everything in your local.conf that is "your project" should be moved to your own distro configuration (MACHINE, image features, package lists). Stuff like where DL_DIR is can be moved to a common site.conf if you wish. Eventually you should end up with a local.conf which just sets DISTRO and some other personal variables.
I would like to apply a few simple changes to the appearance of my IPython/IHaskell/Jupyter Notebooks, such as:
rendered_html :link {
text-decoration: none;
}
However, I can't figure out how to do this. I've tried many of the solutions I've found by searching, e.g., placing CSS in:
~/.ipython/profile_default/static/css/custom.css
but none have any effect, and I suspect that, given the recent changes to the Notebook architecture, the method for accomplishing this has changed and that the instructions I'm finding are out of date.
How do I set custom CSS for my IPython/IHaskell/Jupyter Notebook?
OS X 10.10.4; Xcode 6.4; CLT: 6.4.0.0.1; Clang: 6.1; Python Python 2.7.10 (Homebrew); IHaskell 0.6.4.1, IPython 3.0.0 (answers for 4.0.0 and Jupiter 4.0 also appreciated, as I will upgrade soon).
To add custom CSS to a particular notebook you can use HTML. Add and execute a regular Python code cell with the following content:
from IPython.core.display import HTML
HTML("""
<style>
// add your CSS styling here
</style>
""")
Alternatively (thanks #abalter) use the %%html cell magic:
%%html
<style>
// add your CSS styling here
</style>
Starting Jupyter / IPython 4.1, the custom folder location has changed to ~/.jupyter/custom/. So place your custom.css and custom.js like this:
~/.jupyter/custom/custom.css
~/.jupyter/custom/custom.js
Works for me that way. Credits goes to Liang2
Edit:
If you are missing ~/.jupyter folder, you can use jupyter notebook --generate-config command to generate the folder.
I think the path to your custom.css should be:
~/.ipython/profile_default/static/custom/custom.css
custom folder instead of css folder.
Here is what I did.
From https://jupyter.readthedocs.io/en/latest/use/jupyter-directories.html#envvar-JUPYTER_CONFIG_DIR I found out that you can change the config directory by setting the JUPYTER_CONFIG_DIR env var, then I run jupyter like:
JUPYTER_CONFIG_DIR=./jupyter/ jupyter notebook
My jupyter dir in current dir has the following structure:
jupyter/
- custom/
- custom.css
- custom.js
As of 2021, Jupyter 4.7, Ipython 7, the following location worked for me:
/home/$USER/.jupyter/custom/custom.css
Old answer:
According to Jupyter documentation custom.css should be put into the default_profile/static/custom folders.
You will find the location of your default profile by running in a Jupyter notebook cell:
import jupyter_core
jupyter_core.paths.jupyter_config_dir()
Which gave me:
'/home/sergey/.jupyter'
Afterwards, in .jupyter folder create directory structure like:
static
└── custom
└── custom.css
As you see the desired structure is ~/.jupyter/static/custom/custom.css
This worked for me in Ubuntu 18.04 and latest Jupyter (October 2018)
Per the suggested documentation, I downloaded Anaconda3 first and from within Anaconda Navigator - Jupyter 5.0 Notebook is one of several pre-built options.
I found my CSS file at this location.
C:\Users\YourUsername\Anaconda3\Lib\site-packages\notebook\static\custom\custom.css
I found a nice solution here:
https://martinapugliese.github.io/jupyter-customise/
I needed to add this however:
<style>..</style>
from IPython.core.display import HTML
def _set_css_style(css_file_path):
"""
Read the custom CSS file and load it into Jupyter.
Pass the file path to the CSS file.
"""
styles = open(css_file_path, "r").read()
s = '<style>%s</style>' % styles
return HTML(s)
For base conda environment I found it here:
~/Programs/Anaconda3/lib/python3.6/site-packages/notebook/static/custom
For custom conda environment I found it here:
~/Programs/Anaconda3/envs/[environment name]/lib/python3.6/site-packages/notebook/static/custom
Works under Ubuntu 18.04, conda 4.6.8.
I am running Jupyter on Google Cloud Platform using Tensorflow Docker image and it was located at /usr/local/lib/python2.7/dist-packages/notebook/static/custom/. In Any case, you can find it by searching for it.
Can't add comment due to reputation so I'll post as an answer.
The /custom/custom.css stopped working for me when I generated a config file, but if anyone stumbles to this problem too, the solution is to uncomment the line c.NotebookApp.extra_static_paths = [] in the jupyter_notebook_config.py file and add "./custom/" - or whatever path you chose for your custom css - inside the brackets.
P.S.: OS is Linux Manjaro 5.12 and Jupyter Notebook version is 6.3.0.
For Windows
C:\Users\<username>\.jupyter\custom\custom.css
the above will override the default location: in site-packages https://github.com/jupyter/jupyter/issues/295
If you install it via PIP and not Anaconda, then it's going to be in this folder
C:\Users\<user-name>\AppData\Local\Programs\Python\Python37\Lib\site-packages\notebook\static\custom
From here you can find the custom.css file and edit that to get the changes reflected. You will also have the custom.js file present there as well.
Ubunutu 18.04
Folder
~/venv/lib/python3.8/site-packages/notebook/static/custom
venv is the virtual environment name so the location is relative to your environment's location.
Here, there is a placeholder file, 'custom.css'.
Override it with your own css.
Any machine with Conda installation
C:\Users******.conda\envs\py37\lib\site-packages\notebook\static\custom
Use the path relative to .conda. My environment name is py37
Place your custom css in the custom.css file here.
Reload jupyter notebook.
I've recently installed RubyMine on a second machine and cloned a GitHub repository there.
My application runs exactly the same as on the first machine, but the RM code inspection result is radically different: I get dozens of "No such file to load" errors.
This even though the application runs fine both from the command line and from RM.
In dialog Run/Debug Configurations, I have specified load paths (-I. -I..) in the Ruby arguments.
Does the code inspection not honor the configuration? Or perhaps it's using a different configuration?
A bit late, but you may need to mark the directories that are load path roots in your app within the Rubymine tree - right click and do "Mark Directory As/Load Path Root".
For me the other solutions did not work. However, the problem was that RubyMine detected the wrong ruby version - while rvm for the project was ruby 2.4.1, in RubyMine it defaulted to the last version it had (2.4.2). So going to RubyMine > Preferences > Ruby SDK & Gems and changing the version for the project to the correct one solved it.
If you use the "Mark Directory As/Load Path Root" action, this will apply for IDE autocompletion only. It will not be propagated onto the interpreter (as it would be in PyCharm with Python).
You have to either keep using the -I switch, or configure $LOAD_PATH in your code, or (preferably) set up a Gem project with bundler support. You can then configure the path in a gemspec file. See https://www.jetbrains.com/help/ruby/creating-gem-project.html.
Sources:
https://intellij-support.jetbrains.com/hc/en-us/community/posts/206741945-Load-Path-not-working-at-all-
https://intellij-support.jetbrains.com/hc/en-us/community/posts/206727915-Building-RubyGems-lib-in-load-path-
You can try changing Project Path Mappings and set relative Local Path and Remote Path to get it to work.
We're setting up an OpenSolaris server on Amazon's EC2 service. However, vi/vim doesn't work properly, and pkg doesn't have nano/pico.
Is there any other text-editor maybe?
Sounds like you may just need to set an appropriate termtype to get vi working. Look into the "TERM" environment variable options, perhaps one of those will help you.
You may try copying the nano binaries (or compiling the source), to your user account and running it from there. It worked for me in a similar situation.
Have you looked at http://www.sunfreeware.com/?
SUN is working on the SUNWgnu-nano package to include this in the next release. In the meantime, you can compile the nano sources yourself. It worked for me. To compile, follow these steps:
Make sure you install SUNWgcc package so that gcc is installed.
Download the source package from the debian distribution.
http://packages.debian.org/source/stable/nano
Unzip the package with 'gunzip xxxx.tar.gz' where xxxx.tar.gz is the source package you downloaded.
Untar the package with 'tar -xf xxxx' where xxxx is the unzipped source package.
Go to the source folder. Do a './configure' to create the make file for your system.
Type 'make' to create the binary
The 'nano' binary should be located in the src subfolder. Copy this to '/usr/bin'. And create a soft link for 'pico' to it i.e. 'ln -s /usr/bin/nano pico'
Test it out!
1) Open the Package Manager (System > Administration > Package Manager)
2) Open the Repository settings (Settings > Manage Repositories)
3) Add the Blastwave repository (Name: blastwave, URL: http://blastwave.network.com:10000 )
4) Select the repository in the upper right corner
5) Search for the package 'IPSnano'
6) Select the pacakge
7) Press 'Install/Update'
8) Modify your path to include /opt/csw/bin
(For example $ vi ~/.profile and then add the line above to your path)
9) Logout and in again to reflect the changes
Check whether the correct version of nano is used:
$ which nano
It looks like both Nano and Pico are available as auto-generated packages in the "pending" repository here: http://pkg.opensolaris.org/pending/en/index.shtml. I think they are waiting for someone to follow the verification steps and vouch that they work. Then they can be moved to the contrib repository. You can read more here: http://opensolaris.org/os/community/sw-porters/.