I noticed, when my network is down, Emacs is starting a lot slower. stracing it, it shows how emacs is trying to resolve hostname :S
Anyone knows how to disable this? Why emacs is needs hostname?
Also, I'm keeping .emacs minimal and double checked if some of modules using dns or any network queries.
Thanks.
A very similar issue was recently discussed here.
Related
I've read the TRAMP manual and dozens of forums across the web but I couldn't find an answer to this question. I am trying to set up a link in org-mode that transfers a file from a remote server to my local machine (or vice-versa).
According to the manual I have to write something like
/scp:user#host:filepathonremotemachine
and that's it. No specification of where the file should be moved to, which is weird.
I've tried to do it this way and it simply opened the file (as if I was using ssh); tried other combinations also, without any luck.
There is a specific reason for why I am trying to do this with tramp and not a shell:command link. Any help is very welcome
UPDATE
Apparently TRAMP is less useful than what it promises. That leaves me with the shell:command link option. The problem then revolves around avoiding the openssh window that pops out. The closest solution I found was here and it resumes to setting up an ssh-agent. I am not very familiar with this procedure and I would prefer to use the authinfo.gpg authentication method. Do I have this option? Thanks.
Tramp itself offers just alternative implementations of native Emeacs functions. In this sense, it is dumb, as every library, because it doesn't know what the caller wants.
I'm not an org-mode specialist, but could you please show, which kind of link you have in mind? Without any remoteness, just a link which copies a file locally. Replacing local file names with remote ones will be easy then.
I assume, you need something like an external link, evaluating Lisp code. Like
elisp:(copy-file "/path/src" "/path/target")
The following works (for some definition of "works"):
* link to copy a file
[[shell:scp remote.host.com:/path/to/file /tmp][scp]]
But you must have arranged for passwordless login to the remote host beforehand (e.g. ssh-copy-id your public key to the remote): given that, there is no output in the org buffer, no openssh popup, just the standard question from org-mode asking if you really want to execute the shell command and the file is copied quietly to its destination.
I've seen variants of this question around, but I'm looking for a definitive answer if anyone has one...
We are running a Cloud SQL Postgres instance, and are stuck on restarting the DB after having an export crash out with an unspecified error.
For several hours now our DB has been out of action saying it's restarting.
The options to export, restart, all of that good stuff, are greyed out and unavailable.
There doesn't seem to be a way to force a restart either through the console, or via gcloud command.
Most of the replies I've seen to this question seem to end up with the poster being helped out by Google support. Don't get me wrong, I'd very much appreciate that, but I'd also like to know if there's a way of doing this myself?
Any help greatly appreciated.
Currently, the 'force restart' option is not available for 'PostgreSQL' instance.
There may be several reasons behind the 'stuck' stage of an SQL instance. Not every time, 'force restart' option wouldn't resolves the root/actual cause.
However, if you still think this option needs to be included in the 'PostgreSQL' instance, I strongly recommend opening a 'Feature Request' through the issue tracker. While opening the 'Feature Request', try to include a bit more details about your use case scenario(with or without an example) as well.
I am using a new server that when sshing into requires me the press "return" in order to see my shell prompt. I believe this is causing my emacs tramp to get hung up. When I tried to open a file through tramp on the new server I am repeatedly asked for the password. I read that this could be due to tramp not recognizing the prompt. The prompt is the same as on other servers that work, which makes me think it is this that is causing issues.
I'm thinking the solution would be to add carriage return to the variable tramp-shell-prompt-pattern. How would I do this?
maybe something like:
(setq tramp-shell-prompt-pattern "\r\(?:^\|\)[^]#$%> ]*#?[]#$%>] *\(\[[0-9;]*[a-zA-Z] *\)*")
adding \r to the front of the default?
Also, I don't know if it will be possible to remove this behavior on the server side. I tried creating a .hushlogin file in my home directory, but it had no effect.
I came across this question which addresses the problem of the shell requiring user input. The solution didn't work
(setq tramp-shell-prompt-pattern "^[^$>\n]*[#$%>] *\\(\[[0-9;]*[a-zA-Z] *\\)*")
Thanks for your help. Clearly I'm a novice.
I was wondering if there is a reliable emacs interface for valgrind and its different tools?
I have searched and sadly not found anything.
It would be interesting to have something to jump to the concerning lines via memcheck.
Thank you in advance.
The compilation mode has regexps for this. You may like compilation-shell-minor-mode as well.
Whenever I alter (or even just resave without altering) a Perl file, it completely takes down our backend. I have no idea what the problem could be. Permissions are correct. Encoding is correct. Encoding is UTF-8. Transfer mode was ASCII.
I might not deal with Perl too much but I have no idea what the problem could be. The network admin hosting our website has no idea what the problem could be.
Text editors I tried: Dreamweaver, TextMate, Vim
Operating systems I tried: Mac OS X, Linux (Ubuntu)
FTP clients I tried: Transmit (Mac), Filezilla (Linux (Ubuntu))
It's not that it's bad code, I even tried to open and solely save and my backend still goes down.
The network admin told me that he ran the files through a dos2unix converter and it worked immediately. I of course tried this and it did not, more so it wouldn't make any sense, since I tried this in some of the most respected editors and I don't think it would make such drastic changes to the file type without any user input. (when I say respected editors Dreamweaver is not included in that sentiment).
I personally think it is some sort of server-side issue because I have crossed my t's and dotted my i's in regards to any possible client side issue but I have tried everything. Any opinions as to what the root of this problem is, and any possible solutions? Thanks in advance.
Try setting binary mode in your FTP client. That will allow you to experiment with different line endings (dos2unix) on the client side, without worrying about them being translated during transfer.
I've had this problem in the past and line-feeds were indeed the culprit.
Your editor and/or FTP program may be mangling the linefeeds.
Running dos2unix on the server is a good test as to the problem but not the cause.
Generate an MD5 hash of the file after each step in saving and transport to find where it changes.
You do not say what kind of framework/server you are using.
Maybe the server reloads the file while it is still being written by FTP or whatever? (I.e. that the file is not complete when the server reads it?)
Will a server restart fix the problem once the file is uploaded?
It sounds like you are using dos2unix before the transfer but the network admin is using it after. Perhaps it's doing something different in that case.
How many lines are in the file? What is the file size before and after you save it, after you transfer it, and after transfer and running dos2unix on it?
If this is just a line ending problem, you might point your network admin at http://www.perlmonks.org/?node_id=586942.
Response to rebra: No frameworks are used, and I don't know what kind of server this is on. This is basically a one man project on a shared host which was pretty horribly maintained and I'm trying to clean house.
Yeah that does make sense and I asked the server people about that, one of my first questions actually, but even if that is the case, I can't reboot via Plesk (kind of like cPanel). But thanks for that, you put into technical words/explanation what I was thinking of the whole time.