zsh-users
 help / color / mirror / code / Atom feed
From: shawn wilson <ag4ve.us@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: GnuPG 2.1 with Git, problem in zsh, not in ksh
Date: Wed, 28 Oct 2015 10:33:53 -0400	[thread overview]
Message-ID: <CAH_OBidXA9A=J_h2H9wzjQL2ZrckgvLa_=q66rUoibpG9DSadw@mail.gmail.com> (raw)
In-Reply-To: <20151028111101.GA3212@laptop.local>

check that GPG_AGENT_INFO and GPG_TTY are correct - the syntax of the
former is <socket file>:<pid>:<idr but just set it to 1>

On Wed, Oct 28, 2015 at 7:11 AM, Andreas Kusalananda Kähäri
<andreas.kahari@bils.se> wrote:
> Hi,
>
> I'm a Perl developer using zsh and git, and I sign my git commits using
> gpg2 (from GnuPG 2.1).
>
> In ksh, I'm able to "git commit -S code.pl", but I noticed that this
> stopped working the other week when I started using zsh:
>
> [laptop] ENA % git commit -S submit.pl
> gpg: signing failed: Inappropriate ioctl for device
> gpg: signing failed: Inappropriate ioctl for device
> error: gpg failed to sign the data
> fatal: failed to write commit object
>
> Simply starting up ksh and running the same command works. "Works"
> in this case means git calls gpg2 which uses pinentry to request the
> password, etc.
>
> Since I'm resonably new to zsh, I'm not even sure where to start looking
> for the solution.  The environment variables in zsh are identical to
> those in ksh.
>
> This is my ~/.zshrc file:
>
> # For interactive zsh sessions
>
> # Completion options
> unsetopt AUTO_REMOVE_SLASH
>
> # History options
> setopt EXTENDED_HISTORY
> setopt HIST_EXPIRE_DUPS_FIRST
> setopt HIST_FIND_NO_DUPS
> setopt HIST_IGNORE_DUPS
> setopt SHARE_HISTORY
> unsetopt INC_APPEND_HISTORY
>
> HISTFILE="$HOME/.zsh/history"
> HISTSIZE=10000
> SAVEHIST=5000
>
> bindkey '^R' history-incremental-pattern-search-backward
> bindkey '^G' history-beginning-search-backward
>
> # Input/Output options
> setopt CORRECT
> setopt DVORAK
>
> # Job control options
> setopt BGNICE
>
> # Prompting options
> #setopt TRANSIENT_RPROMPT
>
> PROMPT="[%m] %B%F{red}%1~%f%b %# "
> RPROMPT="%F{blue}%T%f"
>
> # Zle options
> unsetopt BEEP
> setopt VI
>
> autoload -Uz compinit
> compinit
>
> alias ls="ls -F"
>
> export VISUAL="vim"
> export EDITOR="$VISUAL"
>
> --
> :: Andreas Kusalananda Kähäri, Bioinformatics Developer, BILS,
> :: Uppsala University, Sweden
> ::----------------------------------------------------------------------
> :: My other car is a cdr.


  reply	other threads:[~2015-10-28 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 11:11 Andreas Kusalananda Kähäri
2015-10-28 14:33 ` shawn wilson [this message]
2015-10-28 14:47   ` Andreas Kusalananda Kähäri
2015-10-28 15:02     ` Peter Stephenson
2015-10-28 16:22       ` Andreas Kusalananda Kähäri
2015-10-28 18:05         ` shawn wilson
2015-10-28 19:50           ` Andreas Kusalananda Kähäri
2015-10-28 23:49             ` Bart Schaefer
2015-10-29  6:47               ` Andreas Kusalananda Kähäri
2015-10-29 11:47                 ` Simon Ruderich
2015-10-29 17:22                   ` Andreas Kusalananda Kähäri

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='CAH_OBidXA9A=J_h2H9wzjQL2ZrckgvLa_=q66rUoibpG9DSadw@mail.gmail.com' \
    --to=ag4ve.us@gmail.com \
    --cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).