unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: taariqq <taariqq@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Help with PHP setup
Date: Sun, 15 Jul 2018 13:10:18 -0700 (PDT)	[thread overview]
Message-ID: <ea04272b-7ce8-4ac4-9826-8f0e171cacc8@googlegroups.com> (raw)

Hi all, 

I am trying to set emacs up so that I can use it for PHP development.

What I am looking for: 
a) A way to open the files, via my vagrant or lampp setup, in the browser.
b) Update the view in the browser as I save changes to the file in the editor.
c) Switch the view in the browser as I switch from file to file and continue to see the updates upon save.

Not experienced at this stuff and would appreciate a little help. 
Brackets is awesome at this stuff but does not have a good Git integration. VS Code is good at Git and other stuff but the 'preview' end is lacking.

I have tried the 'impatient-mode' and found it jittery. I do not necessarily need 'Live-Preview' ... just update upon save.

If I can configure Emacs I won't have to bother learning other editors and can concentrate on the learning.

Sincerely,
Taariqq


             reply	other threads:[~2018-07-15 20:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15 20:10 taariqq [this message]
2018-07-19 23:57 ` Help with PHP setup Jean-Christophe Helary
2018-07-20  2:32   ` Van L
2018-07-20  4:14     ` Jean-Christophe Helary
2018-07-20  5:47       ` Van L
2018-07-20  7:46         ` Jean-Christophe Helary
2018-07-20  7:52           ` Van L
2018-07-20 23:10 ` Bob Proulx
2018-07-20 23:37   ` Jean-Christophe Helary
2018-07-21  3:53     ` Bob Proulx
2018-07-21 13:17       ` Jean-Christophe Helary
2018-07-22 13:56       ` Jean-Christophe Helary
2018-07-22 15:20         ` Jean-Christophe Helary
2018-07-22 15:36           ` Noam Postavsky
2018-07-22 15:44             ` Jean-Christophe Helary
2018-07-22 15:53               ` Jean-Christophe Helary
     [not found]   ` <mailman.3937.1532129854.1292.help-gnu-emacs@gnu.org>
2018-07-21  3:38     ` Rusi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ea04272b-7ce8-4ac4-9826-8f0e171cacc8@googlegroups.com \
    --to=taariqq@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).