I have ran into a problem involving ITS TECO, which I have a hard time getting past.
The problem is dumping a new standalone INFO.
In ITS, there is a file INFO; INFO EMACS which would seem to do this. INFO$^S :EMACS runs that file and dumps a new EMACS; TSINFO >.
However, that dumped INFO doesn't work fully. It starts EMACS, but doesn't enter INFO mode automatically. The problem seems to be that the INFO EMACS installs a macro calling M(M.M Info Enter$) in FS ^R ENTER, but that macro isn't run in the new INFO.
When I examine the value in FS ^R ENTER in the dumped INFO, it still has the default value, not the macro from INFO EMACS. So it seems dumping the new INFO doesn't save FS ^R ENTER, or running INFO doesn't pick up the new FS ^R ENTER.
How is INFO supposed to install a macro in FS ^R ENTER that persists in a dumped binary?
This was solved by grabbing the text from INFO; INFO EMACS out of the TS INFO binary. It was different from the corresponding source file. Updating the source file with the new text fixed the problem.
Related
I have made some code works today with VS Code. Suddenly when I pressed the CMD + s, VS Code told me:
Failed to save 'example.py': Unable to write file
remote+123.255.255.255/data/example.py' (Canceled: Canceled)
The SSH connection looks like still alive when I opened another SSH remote project.
Then I thought maybe a backup would be a good idea, So I pressed the Saved As button right bottom and input the path /data/example_backup.py which got a warning:
Please enter a path that exists
I still got this warning even if I tried /data/example.py.
Then the show local button reminded me that I can save this file to my local disk. After pressed show local button and choose the local directory, VS Code made some feedback:
Unable to read file 'vscode-remote://ssh-remote+123.255.255.255/data/example.py' (Canceled: Canceled)
But it seems that the backup worked because the file has already been in the local folder.
Is there a workaround to reconnect the SSH remote and save again?
This is followed, for instance, by microsoft/vscode-remote-release issue 5215 (after hibernation) or 4686/3158 (WSL2)
For testing, try the Reload Window command, and see if the connection is restored then (with your file in progress being restored as well, ready to be saved).
I am using Libreoffice 5.2.7.2 on Ubuntu 14.04.
When I do soffice --show filename.odp it always trigger document recovery dialog box even though there is no file to be recovered.
After hitting ok, it will prompt me to select filename.odp to load which defeat the purpose of using soffice --show.
I had edited registrymodifications.xcu on recovery entries. Removed /usr/bin/soffice and reinstall libreoffice.
Still the document recovery dialog box persist with soffice. Any advice is appreciated.
Thank you.
Have you tried resetting the LibreOffice User Profile?
To test --show, create filename.odp as a new presentation and see if the problem still occurs.
I have a full memory dump of a process taken through Task Manager.
Can I determine what the time was on the machine at that moment?
It's displayed in the Command window of WinDbg after you open the dump, as 'Debug session time'.
You can have it printed again with the .time meta-command.
I'm trying to start Libreoffice impress automatically once my raspberry pi has started up.
I created:
.config/lxsession/LXDE/autostart
and added my presentation:
sudo libreoffice -show /home/pi/test.odp
When i execute the command in a terminal, all works fine.
However the autostart doesn't seem to work at boot. Libreoffice starts, but then says it can't find the file...
The file .config/lxsession/LXDE/autostart is used to start applications without root privileges. Therefore, you should remove "sudo" from your code:
libreoffice -show /home/pi/test.odp
That should work as intended. If your presentation need root privileges (I don't see why it would, but anyway), you could use gksudo on your code, then at boot you would see a window asking for your password to proceed. The new code would look like this:
gksudo libreoffice -show /home/pi/test.odp
Important: please note you should not try to open a GUI enabled application with sudo or root privileges, as this can have bad consequences, such as modifying permissions and ownership on program files, which could lead to malfunctioning. If you really need to open a GUI application as root, always use gksudo or gksu.
On the other hand, if you really need to open a program at boot with root privileges, you should look into using the file /etc/rc.local or the cron service for that.
I just got mongo running yesterday, I entered C:\mongodb\bin\mongod.exe, then bought up another command prompt and entered the same thing again, and it was working fine. I ended up shutting it down wrong and now im getting unable to create/open lock file: data/db/mongod/lock because it is being used by another process. I have tried all of what im seeing but getting not recognized errors. It was a little test db, so i want to just get rid of it so i can open mongo again. I deleted the file.lock from my db file as well, but not sure it worked seems like it left and was back again, but it might just be me.
I know this is a super easy problem, just not getting it. Where should i be entering these command, im following the instructions, but i know im not inputing them in the right place because none of them work at all. I tried just inputting them, in C, in C: data/db, i entered C:\mongodb\bin\mongod.exe left it open and opened another command prompt and enter everything in there to. I can't just reset mongodb? Does anyone know what I'm missing maybe it's i have no windows knowledge at all, i'm trying to use it because i know javascript a little php/sql and i'm trying to learn node.js when i had it working in the shell it was great, but with this set up stuff i'm lost. I'm understanding everything there saying but just not where to do it i think.
Someone please lol, i just uninstalled mongodb and reinstalled and same problem.
mongod --repair (is not recognized as internal, or external command)
db.repairDatabase(same,,is not recognized as internal, or external command);
\data\db\mongod.lock (asks how i want to open it)
This is my set up, i think mongod is the problem, but can't get rid of it.
Computer>Windows>data>db
_tmp
joural
local
local.ns
mongod locked file
edit*** not sure if i removed the lock or not but i got it to work. I should have wrote down how i did it but pretty sure this was it.
open a command prompt cd\ enter it cd mongodb\bin enter it open another command cd\ enter it cd mongoDb\bin enter it. in the first command enter mongod then in the other one enter mongo. Don't know if this is right way, but i got me to be able to play with mongodb like i wanted.
try to remove mongod.lock and journal, then restart.