I have installed the anaconda python3 distribution on Windows 7. The python command line works fine. When I type "ipython notebook", however, the server starts and the browser starts and points to the correct local URL (http://localhost:8888/tree), but the resulting page looks awful in my browser. It doesn't look anything like the documentation. It says "Jupyter" at the top, but the elements are not aligned. I've posted a screen-shot at:
Perhaps a .css file (or something) isn't being read correctly. Eventually, I want to run a Julia profile, and I am sure this is a simple problem (I just can't figure it out).
Related
I'm a bit puzzled of what goes wrong, and maybe someone here knows, or has had it before.
First, i got Docker on windows 11.
It runs a ubuntu python container, for all kind of AI stuff.
My local windows PC, has Vscode, i've made a connection to the local container (ssh).
When i open a .ipynb I see the raw file a Json like structure.
That is a bit strange because if i create a new ipynb on windows 11
Its is showing code/markdown cells normally like how vscode shows it normally.
VScode should know what Jupiter notebooks are
So Vscode knows python, everything seems installed in relation to jupyter and remote (localhost) connections.
Does anyone know perhaps what is going wrong here?.
Maybe its something i overlooked, missed.
Or some extra step that needs to be done at VScode, or i open it wrongly ?.
I open the file through the left pane open.. as shown:
I believe all related jupyter notebook stuff is installed in VScode
PS C:\python projects\test> code --list-extensions --show-versions
btwiuse.vscode-remote-server#0.0.5
colinfang.my-nbpreviewer#1.2.2
GitHub.copilot#1.56.7152
jithurjacob.nbpreviewer#1.2.2
ms-azuretools.vscode-docker#1.22.2
ms-dotnettools.csharp#1.25.0
ms-python.python#2022.16.1
ms-python.vscode-pylance#2022.10.40
ms-toolsai.jupyter#2022.9.1202862440
ms-toolsai.jupyter-keymap#1.0.0
ms-toolsai.jupyter-renderers#1.0.10
ms-toolsai.vscode-jupyter-cell-tags#0.1.6
ms-toolsai.vscode-jupyter-powertoys#0.0.6
ms-toolsai.vscode-jupyter-slideshow#0.1.5
ms-vscode-remote.remote-containers#0.255.4
ms-vscode-remote.remote-ssh#0.90.1
ms-vscode-remote.remote-ssh-edit#0.84.0
samghelms.jupyter-notebook-vscode#0.0.2
I am trying to create an shiny app for people that are not R users (they even may be frightened :D).
After the question about server/local app here (How to import remote csv file on a deployed shiny app?), I try to use the shinyShortcut package solution.
I did the following:
devtools::install_github("ewan-keith/shinyShortcut")
library(shinyShortcut)
shinyShortcut(shinyDirectory = "/home/cha/Server",
OS = "unix")
then I got :
So I have all that is normally required (at least that is what I think).
Since I never used the .desktop before, I ran the instruction here.
I put the .desktop on my desktop
Right click and change setting the tutorial did
I allow again from a right click and the .desktop disappears. Everything seemed ok.
However, when I double-clicked on the icon, nothing happened...
I tried to change the web browser or the application to launch it, nothing works.
What did I misunderstand ?
Thanks in advance
Charlotte (Ubuntu 20.04)
I'm new to programming and this forum. My problem is that latex code in markdown cells in a Jupypter notebook opened in vs code won't compile properly. I know that there are several threads already here in this forum and in the internet, but nothing worked so far.
I got to the point where I completely reinstalled my macbook.
So I run the latest VS Code Version on High Sierra, Python is installed via condo and my vs code extensions are python from microsoft and the Jupypter extension.
When VS code is newly installed first everything works but the second time the layout of the Jupyter notebooks changes and latex code won't compile any more.
So The first picture is how it looks on my computer, the second is how it should look. I also recognize, the look of the notebook is slightly different as kernel and host information are (in the second photo) visualized on top of the notebook - below the tabs there is a bar that show the information and also the play sign and so on to run cells.
The weird thing is, that in the beginning, first time after complete installation, on my computer it looked like it should, second time (and every time after that) it changed and it's not working any more without me changing anything.
Does anybody have a clue how to solve this problem?
Thanks a lot!
first pic - my computer
second pic - how it should look
Using atom-editor 1.13 with the love-ide package installed to run LOVE2d 10.2 games (windows 7)
Apparently if you create a conf.lua file in the same folder as your main.lua file you can add some configuations to main.lua. So, I've got these lines of code in my conf.lua to show console.
function love.conf(t)
t.console = true
end
But when I go back to my main.lua and type print("ballz"), all I see is a blank LOVE2d game screen with no extra console window. Not really sure if this is because I'm using atom editor or not. Everything seems to be PATH'ed correctly.
On a side note, whenever I run atom using the love-ide package it always tries to install some "dependecy files" like the hyperclick-love package, and the auto-complete-love package. These fail to install because I don't have git installed.. honestly I really don't know what git is, but neither it, hyperclick, or auto-complete seemed like requirements to run my game, so in the spirit of not installing unnecessary things onto my computer I never installed these things... annoying as it is to see this notification always pop up when I start atom. Anyone know if this is contributing to the issue, or know a way to remove these notifications or auto-download-attempts? My LOVE2d code still seems to run without these packages.
Have you set up the terminal emulator in your configuration?
(Windows only) Try using the lovec.exe executable instead of the normal love.exe. The first one attaches to the console that executed the game, the second one ignores it.
Lua has a buffered output, try adding io.stdout:setvbuf('no') to the top of main.lua
I have my resume online in an html page (www.mysite.com/resume.html). Every time I need a PDF version of it, I use Google Chrome's print dialog to save it as a PDF, which uses my print CSS stylesheet.
I want to be able to navigate to www.mysite.com/resume.pdf to always have an up to date PDF version without having to go through Google Chrome manually. Is there a way to programmatically and automatically create a resume.pdf from resume html? If I can write a script that runs once every 24 hours or something like that, that would be good.
PhantomJS is perfect for this. It invokes an instance of WebKit from the command line which can then be used to output to file such as PDF.
PhantomJS:
http://phantomjs.org/
Specific instructions for exporting screen output to a file:
http://phantomjs.org/screen-capture.html
e.g.:
phantomjs rasterize.js 'http://www.example.com/resume.html' resume.pdf
Chrome has started headless program.
With that, we can create a pdf. e.g. for windows navigate your commandline to
C:\Users\{{your_username}}\AppData\Local\Google\Chrome SxS\Application>
Then hit the command:
chrome --headless --print-to-pdf="d:\\{{path and file name}}.pdf" https://google.com
If you are looking to do this server-side via PHP might I recommend the Browsershot library which leverages the Puppeteer (NodeJS package) and Chrome / Chromium headless browser?
It works really well. Way easier to install and get going than wkhtmltopdf (which is another option that doesn't rely on a NodeJS package nor the Chrome/Chromium headless browser. Personally, I recommend Browsershot solution since wkhtmltopdf has some issues depending on the type of server (Linux distro and version) you're running. That is, the only reliable way to install wkhtmltopdf that I've found is to download and compile from source on the server that you're running and not through a package manager).
Also, if you happen to be needing a solution specifically while working on a Laravel project then there's a wrapper library for Browsershot available.
Check out this tutorial to get started.