From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 44983@debbugs.gnu.org, bugs@gnu.support, dgutov@yandex.ru
Subject: bug#44983: Truncate long lines of grep output
Date: Sun, 13 Dec 2020 17:11:41 +0200 [thread overview]
Message-ID: <838sa1eo5u.fsf@gnu.org> (raw)
In-Reply-To: <87bley7o4a.fsf@mail.linkov.net> (message from Juri Linkov on Sat, 12 Dec 2020 22:42:13 +0200)
> From: Juri Linkov <juri@linkov.net>
> Date: Sat, 12 Dec 2020 22:42:13 +0200
> Cc: 44983@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
>
> > I do not find it problematic. Grep is anyway kind of advanced tool. I
> > think that Emacs "Search for files (grep)" menu option is anyway not
> > user friendly.
> > ...
> > What would be more user friendly would be a form or wizard that would
> > specify if all files are to be searched or recursively, and what would
> > be the search term. That would degrade power of grep but it would be
> > more user friendly to many people.
> >
> > In my opinion I believe that majority of users who ever clicked
> > "Search Files (grep)" gave up after few attempts.
>
> Indeed, "Search for files (grep)" menu option is not user friendly.
In what way is it not user-friendly? It just invokes "M-x grep".
next prev parent reply other threads:[~2020-12-13 15:11 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 8:45 bug#44983: Truncate long lines of grep output Juri Linkov
2020-12-01 15:02 ` Dmitry Gutov
2020-12-01 16:09 ` Eli Zaretskii
2020-12-01 16:46 ` Andreas Schwab
2020-12-01 18:26 ` Eli Zaretskii
2020-12-01 20:35 ` Juri Linkov
2020-12-02 3:21 ` Eli Zaretskii
2020-12-02 9:35 ` Juri Linkov
2020-12-02 10:28 ` Eli Zaretskii
2020-12-02 20:53 ` Juri Linkov
2020-12-03 14:47 ` Eli Zaretskii
2020-12-03 16:30 ` Rudolf Schlatte
2020-12-03 21:17 ` Juri Linkov
2020-12-05 19:47 ` Juri Linkov
2020-12-06 20:39 ` Juri Linkov
2020-12-06 21:37 ` Dmitry Gutov
2020-12-06 21:54 ` Juri Linkov
2020-12-07 2:41 ` Dmitry Gutov
2020-12-08 19:41 ` Juri Linkov
2020-12-09 3:00 ` Dmitry Gutov
2020-12-09 19:17 ` Juri Linkov
2020-12-09 20:06 ` Dmitry Gutov
2020-12-10 8:18 ` Juri Linkov
2020-12-10 20:48 ` Dmitry Gutov
2020-12-09 21:43 ` Jean Louis
2020-12-10 8:06 ` Juri Linkov
2020-12-10 10:08 ` Jean Louis
2020-12-12 20:42 ` Juri Linkov
2020-12-13 10:57 ` Jean Louis
2020-12-13 15:11 ` Eli Zaretskii [this message]
2020-12-13 15:37 ` Jean Louis
2020-12-13 20:17 ` Juri Linkov
2020-12-14 16:15 ` Eli Zaretskii
2020-12-14 20:09 ` Dmitry Gutov
2020-12-24 20:33 ` Juri Linkov
2020-12-24 23:38 ` Dmitry Gutov
2020-12-08 5:35 ` Richard Stallman
2020-12-08 19:15 ` Dmitry Gutov
2022-04-29 11:39 ` Lars Ingebrigtsen
2022-04-29 12:22 ` Eli Zaretskii
2022-04-29 12:41 ` Lars Ingebrigtsen
2022-04-29 13:08 ` Eli Zaretskii
2022-04-30 9:24 ` Lars Ingebrigtsen
2022-04-30 9:36 ` Lars Ingebrigtsen
2022-04-30 10:15 ` Eli Zaretskii
2022-04-30 11:04 ` Lars Ingebrigtsen
2022-04-29 16:02 ` Dmitry Gutov
2022-04-30 9:40 ` Lars Ingebrigtsen
2022-04-30 9:56 ` Lars Ingebrigtsen
2022-04-30 10:09 ` Eli Zaretskii
2022-04-30 10:59 ` Lars Ingebrigtsen
2022-04-30 11:02 ` Lars Ingebrigtsen
2022-04-30 11:12 ` Eli Zaretskii
2022-04-29 17:15 ` Juri Linkov
2022-04-30 0:27 ` Dmitry Gutov
2022-05-01 17:14 ` Juri Linkov
2020-12-01 20:34 ` Juri Linkov
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=838sa1eo5u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44983@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=dgutov@yandex.ru \
--cc=juri@linkov.net \
/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).