unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Deniz Dogan <deniz@dogan.se>
Cc: emacs-devel@gnu.org
Subject: Re: VC and too long command lines
Date: Thu, 21 Jul 2011 10:12:13 -0400	[thread overview]
Message-ID: <E1Qjtz3-0000fL-QF@fencepost.gnu.org> (raw)
In-Reply-To: <4E2821C0.5090409@dogan.se> (message from Deniz Dogan on Thu, 21 Jul 2011 14:55:28 +0200)

> Date: Thu, 21 Jul 2011 14:55:28 +0200
> From: Deniz Dogan <deniz@dogan.se>
> 
> Of course, the command line was simply too long (approximately 66,000 
> characters) for my operating system to handle (Windows 7 64-bit).
> 
> What should Emacs do when this happens?
> 
> I think the most appropriate thing would be to add some functionality 
> which determines the maximum command line length for the current system 
> and if the call exceeds that length, tell the user about it.  Another 
> way would be to e.g. divide the commit into several smaller commits and 
> appending something along the lines of "(commit N of M)" to each commit 
> message.

The former.  The latter is impossible, because to know how to break a
command into several pieces you need to understand the semantics of
that command.  E.g., all pieces but the first might need some
additional command-line switch to tell the program to append the
results to the previous ones, rather than overwriting them.  As
another example, you'd need to use ">>" instead of ">" in all but the
first command.  Etc., etc.



  reply	other threads:[~2011-07-21 14:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21 12:55 VC and too long command lines Deniz Dogan
2011-07-21 14:12 ` Eli Zaretskii [this message]
2011-07-21 14:16   ` Deniz Dogan
2011-07-21 17:02     ` Eli Zaretskii
2011-07-22 20:37       ` Nix
2011-07-23  7:05         ` Eli Zaretskii
2011-07-23 10:36           ` Richard Stallman
2011-07-23 11:05             ` Eli Zaretskii
2011-07-23 17:18               ` Nix
2011-07-21 14:16 ` Daniel Colascione
2011-08-02  3:48 ` Stefan Monnier

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=E1Qjtz3-0000fL-QF@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=deniz@dogan.se \
    --cc=emacs-devel@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.
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).