unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: 63235@debbugs.gnu.org
Subject: bug#63235: 29.0.90; makefile-mode does not recognize Plan 9's mk, mkfile
Date: Wed, 03 May 2023 07:39:12 +0800	[thread overview]
Message-ID: <87ednycnhb.fsf@yahoo.com> (raw)
In-Reply-To: <202305021634.342GYNGn010247@sdf.org> (Van Ly's message of "Tue,  2 May 2023 16:34:23 GMT")

Van Ly <van.ly@sdf.org> writes:

> The makefile-mode is not general enough to make use of Plan 9's user
> space mkfile format and mk command.
>
> This is likely to be considered not a bug.  The expected behavior is
> Emacs would be smart with Plan 9's user space tools.  Specifically,
> the mk command and mkfile format in this case.
>
> The unexpected behavior attempts to compile using the make command and
> not the mk command.  I tried to locate a PLAN9Makefile-mode but didn't
> find one in the command completion mechanism.
>
> steps to reproduce
>  - set PLAN9 and PATH environment variables in shell
>  - verify, mk all, works at the plain shell
>  - start, emacs -Q
>  - visit /tmp/mkfile; makefile-mode does not recognize mkfile
>  - M-x makefile-mode
>  - M-x compile RET; Compile command: make -k, should adapt to mk command
>
> quote
> # example /tmp/mkfile
> all:V:
>   echo This line is left blank intentionally.
>   
> quote ends

The way I understand it, mk is not a variant of Make, and is certainly
not close enough to be supported by Makefile mode.  For starters,
commands are not indented with tabs, but with spaces.

Besides, who uses it in the real world?





  reply	other threads:[~2023-05-02 23:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 16:34 bug#63235: 29.0.90; makefile-mode does not recognize Plan 9's mk, mkfile Van Ly
2023-05-02 23:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-05-04 16:11   ` Van Ly
2023-09-17 15:19     ` Stefan Kangas

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=87ednycnhb.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=63235@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=van.ly@sdf.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).