all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: dptd dptd <dptdescribe@gmail.com>
Cc: 25565@debbugs.gnu.org
Subject: bug#25565: mark-whole-buffer and unnecessary (point) call
Date: Sun, 29 Jan 2017 22:29:06 +0100	[thread overview]
Message-ID: <871svl4kt9.fsf@rosalinde> (raw)
In-Reply-To: <447D8DEA-7B02-44F7-A693-597CE74B6FE4@gmail.com> (dptd dptd's message of "Sun, 29 Jan 2017 22:46:02 +0200")

On Sun, 29 Jan 2017 22:46:02 +0200 dptd dptd <dptdescribe@gmail.com> wrote:

>>> Here is the newest patch.
[...]
>>> * lisp/emulation/viper-cmd.el (viper-mark-beginning-of-buffer):
>>> (viper-mark-end-of-buffer):
>> 
>> There should be no colon `:' after `(viper-mark-beginning-of-buffer)',
>> since `(viper-mark-end-of-buffer)' in the next line is in the same file.
>> 
>>> * lisp/cedet/semantic/senator.el (senator-mark-defun):
>>> * lisp/allout.el (allout-mark-topic): Remove unnecessary argument
>>> `(point)' from calls to `push-mark'.
>> 
>> Steve Berman
>
> I want to contribute to the project but I cannot even prepare the
> patch file correctly... dammit!

If that's the worst problem you have as a contributor, Emacs will be
very lucky indeed! ;-)

Steve Berman





  reply	other threads:[~2017-01-29 21:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28 15:33 bug#25565: mark-whole-buffer and unnecessary (point) call dptd dptd
2017-01-28 19:08 ` Eli Zaretskii
2017-01-28 21:24   ` dptd dptd
2017-01-29  3:40     ` Eli Zaretskii
2017-01-29  7:23       ` dptd dptd
2017-01-29 10:41         ` Stephen Berman
2017-01-29 13:27           ` dptd dptd
2017-01-29 19:48             ` Stephen Berman
2017-01-29 20:46               ` dptd dptd
2017-01-29 21:29                 ` Stephen Berman [this message]
2017-03-24  6:23                   ` dptd dptd
2017-03-24  7:23                     ` Eli Zaretskii
2017-03-24  7:29                       ` dptd dptd
2017-04-28  8:28                 ` Eli Zaretskii
2017-01-29 15:25         ` Eli Zaretskii

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

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

  git send-email \
    --in-reply-to=871svl4kt9.fsf@rosalinde \
    --to=stephen.berman@gmx.net \
    --cc=25565@debbugs.gnu.org \
    --cc=dptdescribe@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.